Share
ReportI was recently tasked with making some custom changes to a client's brand new CRM 2011 system. They wanted an additional field added to the Opportunity entity for a "Topic Category". It was designed to be an option set and be available on multiple entities so I created a global option set for the task. On the Opportunity entity itself, I created a new option set field and used the global option set for the options.
I'm able to add it to the form fine, however, when I try to add it to the views I run into an error saying that the field has been deleted and that I need to remove the field before I can save the view.
The exact error is:
This field has been deleted. To use or save this saved view, you must remove the field.
After turning on tracing and reviewing the logs, I managed to get this error:
The column, fetchxml, has invalid fetch. Error : 'SystemUser' entity doesn't contain attribute with Name = 'bsb_topiccategory'.
This was created when trying to save the view with the newly created field 'bsb_topiccategory' on it. Saving it seemed to be the only way to pop an error out to the log. All of that being said, I'm not entirely sure how to handle the error.
Of course, I considered adding the field to systemuser as well, however, as I'm new to Dynamics, I didn't want to make matters worse with an ignorant decision based on lack of experience.
This question was already asked at StackOverflow and they pretty much gave up trying to help.
Any and all help is appreciated.
*This post is locked for comments
All responses (
Answers (
19
