Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Dynamics 365 Community / Forums / Finance | Project Operations, Human Resources, ... / Import model store int...
Finance | Project Operations, Human Resources, ...
Answered

Import model store into a fresh new installed Database AX2012R3CU11

(0) ShareShare
ReportReport
Posted on by CBNestor 529

Hi all,

I recently installed a new databases for a fresh environment. But I want to install only the ModelStore of our previous customized enviroment.

I haven't been in this process but I tried Exporting and importing by creating a new schema and the applying the changes. Everything looks fine until I Synchronized the recently installed model on target database.

And 4 error shows up after database synchronization on tables I never used before (at least they are not customized)

the problem is that when I go to the AOT and look on this fields I don't find them anywhere. They are in SQL for sure but not showing in the AOT so it makes difficult to track their IDs.

My question. What should be the right process to install a customize modelstore into a new database. I that ok what I am doing?

thanks for your time beforehand.

CASEDETAILBASE
Illegal data conversion from original field CASEDETAILBASE.APPROVED to CASEDETAILBASE.HoursWorked: Unable to convert string data types to anything but INT, or REAL field types (2).
Illegal data conversion from original field CASEDETAILBASE.APPROVEDBY to CASEDETAILBASE.HoursWorkedPayrollIntegration: Unable to convert data types to anything but character field type (0 to 4).
Illegal data conversion from original field CASEDETAILBASE.APPROVEDHOURS to CASEDETAILBASE.LeaveReason: Unable to convert data types to anything but character field type (2 to 4).
Illegal data conversion from original field CASEDETAILBASE.FMLAHOURSAVAILABLE to CASEDETAILBASE.LeaveSchedule: Unable to convert data types to anything but character field type (2 to 4).
Illegal data conversion from original field CASEDETAILBASE.HOURSWORKED to CASEDETAILBASE.LeaveStartDate: Unable to convert data types to anything but character field type (2 to 3).
Illegal data conversion from original field CASEDETAILBASE.HOURSWORKEDPAYROLLINTEGRATION to CASEDETAILBASE.LengthOfService: Unable to convert string data types to anything but INT, or REAL field types (2).
Illegal data conversion from original field CASEDETAILBASE.LEAVEREASON to CASEDETAILBASE.MilitaryFMLAHoursAvailable: Unable to convert string data types to anything but INT, or REAL field types (2).
Illegal data conversion from original field CASEDETAILBASE.APPROVED to CASEDETAILBASE.HoursWorked: Unable to convert string data types to anything but INT, or REAL field types (2).
Illegal data conversion from original field CASEDETAILBASE.APPROVEDBY to CASEDETAILBASE.HoursWorkedPayrollIntegration: Unable to convert data types to anything but character field type (0 to 4).
Illegal data conversion from original field CASEDETAILBASE.APPROVEDHOURS to CASEDETAILBASE.LeaveReason: Unable to convert data types to anything but character field type (2 to 4).
Illegal data conversion from original field CASEDETAILBASE.FMLAHOURSAVAILABLE to CASEDETAILBASE.LeaveSchedule: Unable to convert data types to anything but character field type (2 to 4).
Illegal data conversion from original field CASEDETAILBASE.HOURSWORKED to CASEDETAILBASE.LeaveStartDate: Unable to convert data types to anything but character field type (2 to 3).
Illegal data conversion from original field CASEDETAILBASE.HOURSWORKEDPAYROLLINTEGRATION to CASEDETAILBASE.LengthOfService: Unable to convert string data types to anything but INT, or REAL field types (2).
Illegal data conversion from original field CASEDETAILBASE.LEAVEREASON to CASEDETAILBASE.MilitaryFMLAHoursAvailable: Unable to convert string data types to anything but INT, or REAL field types (2).
CORTANAMODELBUILDPARAMETERS
Illegal data conversion from original field CORTANAMODELBUILDPARAMETERS.ITEMCUTOFFUPPERBOUND to CORTANAMODELBUILDPARAMETERS.FbtMinimalScore: Unable to convert string data types to anything but INT, or REAL field types (2).
Illegal data conversion from original field CORTANAMODELBUILDPARAMETERS.FBTSUPPORTTHRESHOLD to CORTANAMODELBUILDPARAMETERS.InstanceRelationType: Unable to convert data types to anything but character field type (1 to 49).
FBGENERALADJUSTMENTCODE_BR
Illegal data conversion from original field FBGENERALADJUSTMENTCODE_BR.SPEDADJUSTMENTCODEPISCOFINS to FBGENERALADJUSTMENTCODE_BR.IsPovertyFund: Unable to convert data types to anything but character field type (0 to 4).
Illegal data conversion from original field FBGENERALADJUSTMENTCODE_BR.SPEDADJUSTMENTCODEPISCOFINS to FBGENERALADJUSTMENTCODE_BR.IsPovertyFund: Unable to convert data types to anything but character field type (0 to 4).
RETAILPRODUCTATTRIBUTESLOOKUP
Illegal data conversion from original field RETAILPRODUCTATTRIBUTESLOOKUP.INFOCODE to RETAILPRODUCTATTRIBUTESLOOKUP.LabelAttribute1: Unable to convert data types to anything but character field type (0 to 49).
Illegal data conversion from original field RETAILPRODUCTATTRIBUTESLOOKUP.INFOCODE to RETAILPRODUCTATTRIBUTESLOOKUP.LabelAttribute1: Unable to convert data types to anything but character field type (0 to 49).
  • CBNestor Profile Picture
    CBNestor 529 on at
    RE: Import model store into a fresh new installed Database AX2012R3CU11

    Good to know,

    thanks for info. I will duplicate the databases instead and generate similar environment. And stop installing modelstore on new databases x)

  • André Arnaud de Calavon Profile Picture
    André Arnaud de Cal... 291,280 Super User 2024 Season 2 on at
    RE: Import model store into a fresh new installed Database AX2012R3CU11

    Hi Nestor,

    Even standard tables and fields can have different IDs per environment.

  • CBNestor Profile Picture
    CBNestor 529 on at
    RE: Import model store into a fresh new installed Database AX2012R3CU11

    So basically what I am doing should never be made. that is very important to know.

  • CBNestor Profile Picture
    CBNestor 529 on at
    RE: Import model store into a fresh new installed Database AX2012R3CU11

    Hi André,

    thanks for replying

    I understand the ID issue. What I don't get is that those ID conflict that I am facing. Are untouched tables they are not modified and/or customized. And isn't it right that the foundation(sys) Elements they have the same IDs everytime a new database is installed?. Also I dont get Why I cannot see the these fields in the AOT inside the tables described by the error log.

  • Verified answer
    nmaenpaa Profile Picture
    nmaenpaa 101,156 on at
    RE: Import model store into a fresh new installed Database AX2012R3CU11

    Hi Nestor,

    in AX2012 the model database and business database always go hand in hand. You can't move just one of them into another system, there will be issues with wrong object id values.

    If you export/import modelstore, you should get errors in the import in this case - saying that there are ID conflicts. Unless you did it via database backup, not the modelstore export/import tool.

    The only scenario where you can copy modelstore between environments is if the source and target systems have identical object id values. Normally this is the case between staging and production systems. You start by copying the prod system as staging system. Then you can do prod modelstore deliveries from staging.

    In all other cases you should export/import models between the systems, instead of export/import modelstore.

  • Verified answer
    André Arnaud de Calavon Profile Picture
    André Arnaud de Cal... 291,280 Super User 2024 Season 2 on at
    RE: Import model store into a fresh new installed Database AX2012R3CU11

    Hi Nestor,

    When you move a model DB, you also have to use an application DB from the same environment. This is because AOT element numbers are environment specific.

    E.g. If you have two custom fields on a table, in one environment it could be:

    50000 NewFieldX (string)

    50001 NewFieldY (int)

    In another environment the IDs can be different:

    50001 NewFieldX (string)

    50002 NewFieldY (int)

    The DB sync finds the fields based on the ID and thinks that the type of field 50001 needs to be change now. So, ensure you move the modelDB together with a corresponding application database.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

December Spotlight Star - Muhammad Affan

Congratulations to a top community star!

Top 10 leaders for November!

Congratulations to our November super stars!

Tips for Writing Effective Suggested Answers

Best practices for providing successful forum answers ✍️

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 291,280 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 230,214 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

End-of-life Announcement for Microsoft Dynamics GP

Product updates

Dynamics 365 release plans