Try Microsoft Edge
A fast and secure browser that's designed for Windows 10
It's all in the error message:
or the configuration key on the field or on Extended Data Type used by the field is off.
The cube/view uses a field that is not enabled as the configuration key used is off and therefore it can not be created. Nothing to worry about...
well how do i stop the error message or turn the field. It keeping the data dictionary red.
Look in the AOT what configuration keys are used on the table/field/extended data type and enable them (msdn.microsoft.com/.../aa496468(v=AX.10).aspx)
Or just ignore the errors....
Dear David Hutcherson,
I have experienced the same problem in AX 2012. Perform the following activity, it will solve your porblem if incase it still exist.
1- AX 2012 > System Administration Module
4- License Configuration
5- Node > Project I
6- Enable following sub nodes.
7- System will automatically ask and perform the database synchronization.
I did the exactly the steps you suggested. But again i am getting in to the same issue. These fields are having the exyended data type of "ProjBasicHour".
I think that i need to get the correct license key file to solve this issue. Looks like related configuration key is missing for hours journal ( This is AX 2012 R2). Please post your thoughts.
You would think enable the configuration key would work, but it doesn't; neither does enabling the Configuration Key for Retail Head Quarters.
This is a new issue with R2, and CU1 doesn't fix it.
The database synch does complete correctly, and the views are created. The errors you are seeing are part of the database sync validation, these errors and warnings are what it thinks will go wrong should you proceed. If you proceed ignoring the errors you will probably find it synchronise correctly.
If the view is disable for a genuine reason, the fact the views are created won't (or shouldn't) affect functionality, as the data will never be accessed.
In my situation I get 16 errors (4 per table), and 200 warnings. When it completes I get 4 warnings as I have disabled employee compensation. This I want to be disabled so the warnings are perfectly acceptable. If I do enabled them I get now errors after it completes.
The trick to solve it, comes with the way Microsoft wrote it. They used the data dictionary as part of the data sync validation, and if any validation errors occur, this appears to not be updated.
So, if you enable all the keys so this completes without warning (which means most, except for country features - but don't enable any of the "Keep" keys unless you are upgrading), the database synchronises correctly after this point.
Of course you may want (and this is completely reasonable) to disable elements you don't need; do this after it succeeds - that way all the bogus errors and warnings don't appear - only the genuine warnings.
The real problem you may find is that some queries (HR) are based on views, and compiling the query node will give you an error at the end of the process without a clue to the query that caused it. This means you can't build the CIL, leading to obvious issues down the line. The solution was to remove the config keys that stopped two HR views from being generated. I believe this is meant to be solved in R2.
I met the same problem in AX2012 R2. I want to know how do you solve this issue later?
Thank you in advance.
I faced the same situation when installing Dynamic AX 2012,
I didn't know where To Change Configuration settings
Please suggest me your thoughts how can i resolve this issue.
Thanks in advance. ..