Personalized Community is here!
Quickly customize your community to find the content you seek.
Have questions on moving to the cloud? Visit the Dynamics 365 Migration Community today! Microsoft’s extensive network of Dynamics AX and Dynamics CRM experts can help.
2022 Release Wave 2Check out the latest updates and new features of Dynamics 365 released from October 2022 through March 2023
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Community | FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
I am trying to delete a custom field from an entity it shows it has dependencies to two custom vies and a system view. I have removed the field from all views and published the solution and it still appears as the dependency relationship exist. In order to remove it from the custom views, I deleted the sub-grids on forms the entity existed and had to delete the view. Unfortunately, I cannot do the same for the system view.
Microsoft Dynamics CRM 2015
Yes. I already did that. The system view does not have the field yet it is still referencing a dependency.
Do you have this attribute used in sorting colums for that system view?
you need to remove from there also..and if quick find view then remove or uncheck from find columns also..publish you changes.
Hope this will help
Is it a global option set?
Did you publish all customizations, not just the single entity?
You are not alone.
We have struck this before on the odd occasion.
There seemed to be no logic.
For us the field had been removed from everywhere it was telling us to remove it from, and was no-longer actually referenced by anything we could configure/code, but the dependencies persisted.
We made the field non-searchable (so people didn't see it in Advanced Find lists), renamed it as (do not use) and left it in the solution.
Not ideal, but generally not the end of the world.
That was it. I forgot I had filter criteria in the view that utilized the custom field. I was now able to remove.
I had the same issue and found if I do the following actions then I am able to delete the field.
1. Make field not searchable and rename the field
2. Go to Quick Find view and click "Add Find Column", uncheck all fields and select the ones you want it to search again
3. Publish the entity
I had a similar situation. the dependency of the field was in the quick search view (although i removed the field from the display columns). it was still stuck in this view as a dependent field. For me, what strangely worked was to change the field that was checked in the "Searchable Columns" list, to another random field (the one that was checked was of type lookup, and the one that i chose to check was a simple text type). It was strange because the checked field had nothing to do with the problematic dependent field, but this change, kind of "refreshed" the view, releasing the dependency and allowing the field to be delete.
Hope this helps someone
I had the same issue.
My solution was that i went to Views of the from and there was in search bar riht on top.I delete it and it helped.Hope i save some time to somebody.
Business Applications communities