Unanswered

How to break the component library with a single quote / ' mark

(2) Share

Report

Posted on by Ben Thompson

1,400

I'm posting this here as it's fixed so I can't issue a support request but partly in case others have the same issue and partly as a bug report.

If you have a single quote / apostrophe in the description-key of the control element of the manifest i.e.

<control namespace="hdn" constructor="SelectForm" version="0.0.1" display-name-key="Select Form" description-key="A select control to allow the selection of an entity's form" control-type="standard">

instead of

<control namespace="hdn" constructor="SelectForm" version="0.0.1" display-name-key="Select Form" description-key="A select control to allow the selection of an entitys form" control-type="standard">

The control will successfully import but when you try to select any control in Field Properties you will see the following error

Component selection if a component has a apostrophe in the description

Categories:

Power Apps Pro Dev & ISV

I have the same question (0)

All responses (3)

Answers (0)

Sort by

psycrkz1 Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Thanks for your reporting and we will try to repro on our OOB environment with solution import that contains a form with single quote in the description

And hopefully we would file a bug for this issue and release the fix in the future weekly update

Was this reply helpful? Yes No
JP-09110045-0 Microsoft Employee on at

Like (3)

Report
Copy link

Link copied!

Hi @ben-thompson,

This issue is a known issue that is caused by a parsing issue in form designer.

To get around this issue, other than just removing it, you can also use a resx file containing the string with the apostrophe and use a key in description-key to point to it.

Using a resx file is a better way to specify more complex strings as having it in the key can have these side effects.

Was this reply helpful? Yes No
mmcguinness 8 on at

Like (1)

Report
Copy link

Link copied!

Thanks for this post Ben, you're a life-saver! This solved an issue we've been having. It's been with MS support for over a week, and they can't solve it.

It would be great if someone at MS could let the support team know that this known issue.

We're experiencing pretty serious issues around PCF control parameters, and in some cases, have had to actually restore the whole environment from backups because the form editor gets so badly broken parsing PCFs you can't select any custom or out of the box control for subgrids. Parsing XML reliably shouldn't be this hard in 2020. Additional issues we've run into:

- Adding/removing control parameters can cause generic errors in the form editor, and custom control must be removed from form before form can be saved.
- Order of properties vs. data-set not documented and causes stability issues.
- Bound properties don't seem to work when control is a data-set (control imports but doesn't appear in the form editor).
- Order of bound vs. input properties seems to be an issue, but not documented.

Anyways, thanks again for this tip Ben!

Was this reply helpful? Yes No