update readonly column for Dynamics 365 Finance
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. Yet the data export / import both in D365FO and AX2012 may bypass the AOS validation 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 entity. Optionally, 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:
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 and breaks the database consistency.
posted on 2025-02-18 15:35 lingdanglfw 阅读(3) 评论(0) 编辑 收藏 举报
【推荐】国内首个AI IDE,深度理解中文开发场景,立即下载体验Trae
【推荐】编程新体验,更懂你的AI,立即体验豆包MarsCode编程助手
【推荐】抖音旗下AI助手豆包,你的智能百科全书,全免费不限次数
【推荐】轻量又高性能的 SSH 工具 IShell:AI 加持,快人一步
· DeepSeek 开源周回顾「GitHub 热点速览」
· 物流快递公司核心技术能力-地址解析分单基础技术分享
· .NET 10首个预览版发布:重大改进与新特性概览!
· AI与.NET技术实操系列(二):开始使用ML.NET
· 单线程的Redis速度为什么快?
2016-02-18 Dynamics AX Hostory