# Apply the property expressions

Open the app in Power Apps Studio and select the control/property named in each comment in `long-text-formulas.fx`. Paste only that property's expression. Do not paste the entire file into OnSelect or import it as an app.

- The new modern Text control must be directly inside its field's data card for `Parent.Default` and `Parent.Width` to refer to that card.
- `DataCardKey49` is the example heading. Replace it in every copied card with that card's actual heading control name.
- `frmRequestViewing` is the example form. Replace it with your Edit form's actual name for optional View/Edit/New switching.
- The original input and replacement Text control use opposite Visible conditions. For a dedicated viewer, hide the input with `false` and leave the Text control visible instead.
- `Text2` is the example modern Text control with AutoHeight on. A data card grows to fit it, and every card in a row matches the tallest card. A card never shrinks below its own Height, so the optional card Height formulas let a card shrink to short text. They assume `Text2` sits under the heading and nothing visible in the card sits below it. In the shared-form version, replace `300` with the card's original Height; the editing branch avoids `Text2.Height`, which doesn't update while the control is hidden.
- `Text2_1` names a second example Text control used in a dependent-label position formula. Use this only if repairing an applicable reference.
- 24, 48, 4 and 8 are example layout spacing. Adjust them to your app's padding and width; on a narrow card, reduce 48 so the text keeps a usable width.
- Keep the original editable input, its data card Update binding, and validation behavior on any form that can submit edits. The display label reads defaults and is not a live mirror of unsaved input.
- ColorValue adds the example background through a Power Fx property; it does not change the app's theme globally.

The formulas use comma argument separators as shown in the example. There are no external libraries or runtime dependencies beyond the existing Power Apps form and controls. Use the article's record-length, screen-width, mode-switching and save/cancel checks before publishing.