15
Hello All,
When I import specific GER configurations from LCS directly through D365. I receive these validations errors.
Has anyone come across this? If so, how do I fix this?
Even though they are only warnings, I consistently will get errors when trying to "run" the configurations.
Please help! I have read countless blogs/manuals and are coming up with nothing.
Yes. I am using LCS repository to import the ER configurations so I will try using the global repository instead so thank so the link!
I have tried testing the Purchase Order excel in a testing scenario but I still get an xml download rather than an excel. I get about 250 "is not bound" errors as well. This is using the PO imported directly from LCS.
Hi Sandra,
Here is the link to the LCS entry for the validation matter. To monitor the progress of the investigations, please use the "Notify me" function to receive an email when the investigations is completed:
KB 4570009 fix.lcs.dynamics.com/.../Details
Thus, could you please clarify if you are using LCS repository or Global repository for importing the ER configurations? Indeed, the LCS repository for ER configurations has a lot of challenges, and is not considered for primary usage going forward. Microsoft has developed Global repository of Configuration services and it should be used as a standard place to store and operate with ER configurations. Please consider the below documentation for further references:
docs.microsoft.com/.../er-download-configurations-global-repo
There are limited functionalities called out when running the format from ER framework directly. So the recommendation would be to set up your environment and use the "Purchase order (Excel)" for a PO testing scenario.
Also, if you manage to recreate the exact error, please open a Support Ticket with Microsoft to get this investigated further.
With kind thoughts,
Laura
Hi Laura,
Thanks for the reply!
The second copied image are more warnings I received when I was importing all the GER configurations from LCS to my environment. This was the second time I tried the "import all" action. I have not tried importing all since the last MS update so I'm not sure all the same warnings will show.
In order to organize, I just imported Purchase Order which gave the two warnings you spoke to above.
Yes. I am running this for testing directly from ER framework. I did try adding a custom field through my derived order model configuration and got more binding errors in relation to 'PurchaseOrderInquiry' not being bound on almost all the fields in the purchase order.
After the most recent MS update, when I try running the configurations, an xml file is created and downloaded to my pc. I am not sure why that is happening? So I am trying to recreate that exact error message again but I can't anymore after re-importing again. I just get left with a created xml document.
Thanks,
Sandra
Is there any other more recently updated resources to look at? I have tried running through tutorials in the MS docs but I am not using Sharepoint and whether that has an impact, those changes do not show in the ER framework and vice versus.
Hi Sandra,
Thank you for reaching out to Microsoft community.
While validating the Purchase order (Excel) configuration, I received the same 2 warning messages and I escalated this internally towards Microsoft product group since the initial formula containing WHERE clause is correct from a technical point of view, and FILTER function does not actually apply here.
Could you please clarify when exactly do you receive the other warnings and error messages, please? Are you running this format just for testing directly from Electronic Reporting framework > Reporting configurations? Are you having any customized fields added to the format? Or do the errors still occur after removing the existing imported format and model mapping, and re-importing them again?
If there is no helpful information, then please open a Support Ticket with Microsoft to get this investigated further.
With kind thoughts,
Laura
Hi Andre,
Thanks for the reply.
Purchase order (Excel) version 73.56 created on 6/15/20
D365 version: Installed product version : 10.0.10 (10.0.420.10007)
- Installed platform version : Update34 (7.0.5600.35524)
In previous versions, the same warning persists.
Thanks!
Hi Sandra,
Which exact configurations did you try to import and what exact version of Dynamics 365 are you using?
#1
André Arnaud de Cal...
292,892
Super User 2025 Season 1
#2
Martin Dráb
231,772
Most Valuable Professional
#3
nmaenpaa
101,156
Moderator
Share
Report
All responses (
Answers (
