After that, I started to put my knowledge into work and encountered some errors.
I didn’t find too much information about them so I decided to write a post about data entity errors.<\/p>\n\n\n\n
Error after adding range<\/h2>\n\n\n\nOccurence<\/h3>\n\n\n\n
When I try to add a range to my data source, Visual Studio won\u2019t let me build the project. The following error message shows up: The \u2018IsPrimary\u2019 field was one of the entity\u2019s fields. Renaming the range or the field did not solve the error. After you modify an entity that\u2019s already been in the Data entity list \u2013 or in the DMFEntity table \u2013 and then you rebuild the project, you\u2019ll get something similar to the following error list.<\/p>\n\n\n\n You can delete the affected entities from the Data Entities list. (System Administration \u2013 Data management node.) If the entity has corresponding data projects, delete them first. Then try deleting the entities again and rebuild the project. Even after refreshing data entities, the custom data entity was still not shown in the list. However, it could be displayed by OData.<\/p>\n\n\n\n The custom entity had the same label as a system entity that already existed. I created a new different label for it and after that it was displayed in the data entities list.<\/p>\n\n\n\n I imported a non-standard table from an old version of AX (AX 4.0) through xml. Then I created a data entity and used this table as one of the datasources. I didn’t get any errors when modifying properties and saving the object, but when I built and synchronized it, I got the following error list.<\/p>\n\n\n\n After looking around on professional forums, I stumbled upon a solution<\/a> that solved my issues. It suggested that this error might be caused because of table relations are not set up correctly and to check the cardinalities of the relations. Fixing errors can be time consuming and sometimes frustrating. <\/p>\n\n\n Introduction My previous article was about data entities.After that, I started to put my knowledge into work and encountered some errors.I didn’t find too much information about them so I decided to write a post about data entity errors. Error after adding range Occurence When I try to add a range to my data source, […]<\/p>\n","protected":false},"author":4,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_et_pb_use_builder":"","_et_pb_old_content":"","_et_gb_content_width":"1080","footnotes":""},"categories":[19],"tags":[25,83],"class_list":["post-800","post","type-post","status-publish","format-standard","hentry","category-dynamics-365fo","tag-msdyn365fo","tag-data-entity"],"_links":{"self":[{"href":"https:\/\/daxvisionerp.com\/home\/wp-json\/wp\/v2\/posts\/800","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/daxvisionerp.com\/home\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/daxvisionerp.com\/home\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/daxvisionerp.com\/home\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/daxvisionerp.com\/home\/wp-json\/wp\/v2\/comments?post=800"}],"version-history":[{"count":1,"href":"https:\/\/daxvisionerp.com\/home\/wp-json\/wp\/v2\/posts\/800\/revisions"}],"predecessor-version":[{"id":1374,"href":"https:\/\/daxvisionerp.com\/home\/wp-json\/wp\/v2\/posts\/800\/revisions\/1374"}],"wp:attachment":[{"href":"https:\/\/daxvisionerp.com\/home\/wp-json\/wp\/v2\/media?parent=800"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/daxvisionerp.com\/home\/wp-json\/wp\/v2\/categories?post=800"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/daxvisionerp.com\/home\/wp-json\/wp\/v2\/tags?post=800"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
A local variable named ‘IsPrimary’ cannot be declared in this scope because it would give a different meaning to ‘IsPrimary’, which is already used in a parent or current scope to denote something else.<\/em><\/p>\n\n\n\n![\"\"](\"http:\/\/daxvisionerp.com\/wp-content\/uploads\/2020\/03\/image-5.png\")
<\/figure>\n\n\n\nSolution<\/h3>\n\n\n\n
Since it was a NoYes field, it was not mandatory to be in the entity field list because the range filtered the value already. I deleted the \u2018IsPrimary\u2019 field from the field list and now the project can be built without errors.<\/p>\n\n\n\nErrors after project rebuild<\/h2>\n\n\n\n
Occurrence<\/h3>\n\n\n\n
![\"\"](\"http:\/\/daxvisionerp.com\/wp-content\/uploads\/2020\/03\/image-6.png\")
<\/figure>\n\n\n\n\n
Solution<\/h3>\n\n\n\n
This solution solves the errors only until the next rebuild.
The data entity’s label causes the real problem here. System data entities usually use the same label as their main data source’s label. Your data entity can easily get the same label if your entity was made with the help of the wizard.<\/p>\n\n\n\nData entity not shown in Data entities list <\/h2>\n\n\n\n
Occurrence<\/h3>\n\n\n\n
Solution<\/h3>\n\n\n\n
Failed to parse data entity view queries for following data entities<\/h2>\n\n\n\n
Occurrence<\/h3>\n\n\n\n
\n
Solution<\/h3>\n\n\n\n
I noticed that on the table I imported, cardinality properties were not filled in. After filling them out correctly, the errors were gone and the data entity was working.<\/p>\n\n\n\nSummary<\/h2>\n\n\n\n
I hope I could help you finding the solution that you were looking for.<\/p>\n\n\n\n