You’re offline. This is a read only version of the page.
306
In my model-driven app, I had a tab on a form with several controls on it. I deleted that tab. Now I want to delete one of the fields that was on that tab from the table. But it won't let me because the dependency still exists on that form. I've tried adding the field back onto the form and deleting it again, but the dependency is still there. I even tried adding a new tab, giving it the same properties as the original tab, adding that field to it, save/publish, delete the field again, save/publish, and dependency is still there. How can I get rid of that dependency?
Had same issue when trying to delete bunch of fields. In my case,
* Added the field back to the form
* Applied 3rd party controller (as it was before removing field from the form)
* Save and Publish
* Change controller back to default one
* Save Publish
* Remove field from the form.
It didn't just stop showing form dependency for this field but all other that previously giving me trouble.
I've seen this behavior too. What appears to happen is that when you add a PCF to a form it gets added to the XML in two places: at the top of the form XML to register the presence of the PCF and inline in the xml on the control you are replacing. Sometimes when you remove the control (or remove its tab or its section) only the inline portion gets excised and the declaration at the top of the form XML persists. When this happens you're pretty much SOL, within the UI at least (re-adding and deleting won't get you there).
I have found only two workarounds for this:
- Delete the form and recreate it or
- Crack open the customizations XML and delete the XML node for the PCF
For the record, as much as we all know XML editing is a baaaaad idea, I have found in this circumstance it is easy and safe, so I would actually recommend it here if deleting and recreating your form will cause you problems (i.e. if you have downstream customizations to the form and replacing it isn't a practical option).
This is a known issue and we are working on it ..can you please log a support case and they can run mitigation script ..
I am Enquiring other workaround options . Will update the thread.
Thanks,
Hemant
Hi @DianaBirkelbach ,
I'm the only person making changes in this environment right now. When I view dependencies for the field, it shows the form that it used to be on. When I double click the dependency, it opens the form editor and that field shows on the Unused Fields list.
Hi @tschopp ,
Hm.. I haven't encountered this. Are you sure that the dependency is not on another form? If somebody made another form, maybe he/she got the PCF automatically without even noticing?
Kind regards,
Diana
#1
WarrenBelz
109
Most Valuable Professional
#2
Michael E. Gernaey
82
Super User 2025 Season 1
#3
MS.Ragavendar
72
Share
Report
All responses (
Answers (
