web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Apps / RTE Control's Custom C...
Power Apps
Suggested Answer

RTE Control's Custom Configuration URL setting is lost when managed solution is updated

(1) ShareShare
ReportReport
Posted on by 311
I have the Rich Text Editor Control setup on a custom table's main form. Using an unmanaged solution, I updated the control settings with a custom value for the "Custom Configuration URL" static value setting. When I import a managed solution that contains that table and form, the Custom Configuration URL setting is lost. How to prevent that from getting erased?
Categories:
I have the same question (0)
  • Suggested answer
    RaghavMishra Profile Picture
    261 on at

    Hi,

    What you're seeing is solution layering behavior, not a bug.

    The RTE control's Custom Configuration URL (Static value) is a property on the form control component, which lives inside the form's XML. Per Microsoft Learn:

    • Unmanaged customizations sit in the unmanaged layer, which is above managed layers.
    • When you import a managed solution that contains the same form, the form is updated in its managed layer — and depending on how the form was exported, your unmanaged property change can be replaced by the form merge logic (“Last one wins” between managed solutions, with the unmanaged layer overlaying on top only for the customizations Dataverse recognized as unmanaged).

    How to make the Custom Configuration URL stick:

    1. Set the Custom Configuration URL inside the same solution you're shipping as managed — make the change in the publisher's unmanaged dev environment, export the form as part of the managed solution, and import. The property travels with the form's managed layer.
    2. If you must add it post-import in the target environment, put the change in a separate unmanaged solution that does NOT also include the same form from the imported managed solution. Otherwise, reimporting the upstream managed solution will overwrite the form's control XML.
    3. Verify in Solution → Show dependencies / View layers that your Custom Configuration URL value is on the layer you expect.

    📚 References (Microsoft Learn):

    Found this helpful? Please mark ✅ “Does this answer your question?” so others searching for the same issue can find it quickly. A 👍 on “Was this reply helpful?” or a ♥ Like is also much appreciated!

    Raghav Mishra — LinkedIn | PowerAI Labs

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Season of Sharing Community Challenge Launch!

Jump in, show your community spirit, and win prizes!

Kudos to our 2025 Community Spotlight Honorees

Expanding mentorship, skilling, and AI innovation

Congratulations to the May Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Power Apps

#1
Valantis Profile Picture

Valantis 424

#2
WarrenBelz Profile Picture

WarrenBelz 355 Most Valuable Professional

#3
11manish Profile Picture

11manish 290

Last 30 days Overall leaderboard