Источник:
http://erconsult.eu/blog/overwrite-a...ion-in-d365fo/
==============
Updating an arbitrary read-only field in a configuration table in may pose a challenge in Dynamics 365 for Finance and Operations, especially in the production environment.
Many options may only be set once, for example the
Use warehouse management processes mode of a warehouse, or the
Revenue recognition accounting rule in a project group. However, the data export / import entities both in D365FO and AX2012 may bypass the AOS validation and break the database consistency as long as a data entity exists.
Here is how: open the
Data management workspace and create an Export data project. Pick the respective data and reduce the number of exported fields in the mapping to the minimum: the entity key and the read-only parameter in question.
Drill down into the
Entity structure and turn off the
Run business validations checkbox:
Then use the
Modify target mapping button to clear the
Call validate Field method checkbox from the entity attribute in question:
Export the data, download the ZIP data package, extract the Excel file and amend the parameter in the file as desired. Then re-pack the ZIP data package with the updated file (replace the original), create an Import data project, upload and import the package. With a high probability the Data management engine is going to bypass any application logic and update the existing record without further asking.
As a matter of fact, this method is even more brutal than the
table browser (
RIP, dear table browser, you are truly missed), since it ignores field properties set at the table metadata level.
The post
Overwrite a read-only configuration in D365FO appeared first on
ER-Consult.
Источник:
http://erconsult.eu/blog/overwrite-a...ion-in-d365fo/