Skip to main content

Notifications

Announcements

No record found.

Microsoft Dynamics AX forum
Answered

Problems Snychronizing database

Posted on by 400
Every time I synchronize the data dictionary I get 4 tables (with no customizations) that have errors. ProjJournalTransFeeUnpostedView, ProjJournalTransHourUnpostedView, ProjTransBudgetCube, and ProjTransPostingCube The text for the error are like the following:
·     Synchronize database Specified field Qty of datasource ProjJournalTrans does not exist in the database or the configuration key on the field or on Extended Data Type used by the field is off. The view ProjJournalTransFeeUnpostedView can not be created in the database.
·     Synchronize database Specified field Qty of datasource ProjJournalTrans does not exist in the database or the configuration key on the field or on Extended Data Type used by the field is off. The view ProjJournalTransHourUnpostedView can not be created in the database.
·     Synchronize database Specified field StatementConsumpHourCost of datasource ProjParameters_1 does not exist in the database or the configuration key on the field or on Extended Data Type used by the field is off. The view ProjTransBudgetCube can not be created in the database.
·     Synchronize database Specified field StatementPLHourCost of datasource ProjParameters_1 does not exist in the database or the configuration key on the field or on Extended Data Type used by the field is off. The view ProjTransPostingCube can not be created in the database.
Thanks for the help in advance. 
  • Nick Vara Profile Picture
    Nick Vara 5 on at
    RE: Problems Snychronizing database

    Hi All,

    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. ..

  • jxqiao Profile Picture
    jxqiao 10 on at
    RE: Problems Snychronizing database

    Dear David Hutcherson,

    I met the same problem in AX2012 R2. I want to know how do you solve this issue later?

    Thank you in advance.

    Jianxin

  • Simon Buxton Profile Picture
    Simon Buxton 130 on at
    RE: Problems Snychronizing database

    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.

  • Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: Problems Snychronizing database

    Dear Ahmed,

    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.

    Thanks

    Uday

  • Suggested answer
    Ahmed Muhammad Alam Profile Picture
    Ahmed Muhammad Alam 3,085 on at
    Re: Problems Snychronizing database

    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

    2- Setup

    3- Licensing

    4- License Configuration

    5- Node > Project I

    6- Enable following sub nodes.

       a- Fees

       b- Hours

    7- System will automatically ask and perform the database synchronization.

  • David Hutcherson Profile Picture
    David Hutcherson 400 on at
    Re: Problems Snychronizing database

    thanks :)

  • Verified answer
    Xander Vink Profile Picture
    Xander Vink 2,550 on at
    Re: Problems Snychronizing database

    Look in the AOT what configuration keys are used on the table/field/extended data type and enable them ([url]msdn.microsoft.com/.../aa496468(v=AX.10).aspx[/url])

    Or just ignore the errors....

  • David Hutcherson Profile Picture
    David Hutcherson 400 on at
    Re: Problems Snychronizing database

    well how do i stop the error message or turn the field. It keeping the data dictionary red.

  • Suggested answer
    Xander Vink Profile Picture
    Xander Vink 2,550 on at
    Re: Problems Snychronizing database

    It's all in the error message:

    [quote]or the configuration key on the field or on Extended Data Type used by the field is off.[/quote]

    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...

Helpful resources

Quick Links

Replay now available! Dynamics 365 Community Call (CRM Edition)

Catch up on the first D365 Community Call held on 7/10

Community Spotlight of the Month

Kudos to Saurav Dhyani!

Congratulations to the June Top 10 community leaders!

These stars go above and beyond . . .

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 287,773 Super User

#2
Martin Dráb Profile Picture

Martin Dráb 225,513 Super User

#3
nmaenpaa Profile Picture

nmaenpaa 101,148

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans