Electronic reporting - Error when importing XML configuration to another environment

(0) Share

Report

Posted on by Zen_Raj

177

I am trying to export XML config from one box into another environment. When I try I get this error. I know that I am supposed to be importing from parent > child when doing XML. So the next one I am trying to import after Payment model and Derived payment model is Payment model mapping to destination. Please see second screenshot for the list of all the configs in the original environment that I need to import into the other one - what order should I be doing this in? Thanks

Additionally, do I need to have imported any part of the config from the LCS repository before continuing to import XML? Or can I do all the importing strictly through XML, from parent to child?

Categories:

Financial Management

Data Integration

Development / Customization / SDK

I have the same question (0)

All responses (10)

Answers (3)

Zen_Raj 177 on at

Like (0)

Report

RE: Electronic reporting - Error when importing XML configuration to another environment

Ties,

I am not sure what I would do without you. Thanks, this solved my issue!

Was this reply helpful? Yes No
Verified answer

Ties Philippi 960 on at

Like (0)

Report

RE: Electronic reporting - Error when importing XML configuration to another environment

Hi Zen

I don't think you can rebase, as this is a Microsoft configuration.

So if you just import version 19 of the payment model (either from LCS or by exporting it from your other environment this should not matter) and you should be fine.

Was this reply helpful? Yes No
Zen_Raj 177 on at

Like (0)

Report

RE: Electronic reporting - Error when importing XML configuration to another environment

Hi Ties,

Could you please explain further? From my understanding you are saying, my configs are using version 26. My model mapping to destination is erroring because it is looking for 19.

Does that mean I have to rebase my model to use the lower 19 one? When I try to rebase the model mapping to destination it is not possible

Was this reply helpful? Yes No
Verified answer

Ties Philippi 960 on at

Like (0)

Report

RE: Electronic reporting - Error when importing XML configuration to another environment

By the way.

If you look at the error you see a GUID. This is the way ER stores the configuration references. This GUID is the payment model.

After the GUID you see a comma and a number. This is the version number. So in this case it tells you it is missing payment model version 19.

Best regards

Ties

Was this reply helpful? Yes No
Verified answer

Ties Philippi 960 on at

Like (0)

Report

RE: Electronic reporting - Error when importing XML configuration to another environment

Hi Zen,

The error you show tells that the base can not be found. This means that the configuration ( the payment model mapping) can be found however the correct version can not be found.

If you look at the version number it tells you what the version of the parent is.

So 14.25 for example means that it needs parent version 14 and the configuration itself is version 25.

So in this case you can do 2 things, either rebase the child configuration in the source environment. This works means that version 14.25 would become version 15.25 or whatever parent version is available. This does require validation of the effect of the changes in the parent configuration. Alternatively you could export and import the Required version by the child configuration.

Best regards

Ties

Was this reply helpful? Yes No
Suggested answer

Ludwig Reinhard Microsoft Employee on at

Like (0)

Report

RE: Electronic reporting - Error when importing XML configuration to another environment

Ah, you modified the model in your one environment and want to move this adjustment to another environment, is that right?

This should work via the export/download and import way you tried.

Another thing that you can try doing is making the model and configuration that was adjusted shared. This syncs it back to the asset library on LCS from where you can distribute it to other environments.

Best regards,

Ludwig

Was this reply helpful? Yes No
Zen_Raj 177 on at

Like (0)

Report

RE: Electronic reporting - Error when importing XML configuration to another environment

I see what you mean.

When you say download from LCS, do you mean only the model? I can still import the customized model, format, and model mapping from XML right? Just import the base model first?

Was this reply helpful? Yes No
Suggested answer

Ludwig Reinhard Microsoft Employee on at

Like (0)

Report

RE: Electronic reporting - Error when importing XML configuration to another environment

Hi Zen,

The different versions might be an issue. An alternative to trying to shift the ER model/configuration this way would be to download the model and configuration once again from LCS. This is the safest and best way as things might have changed. By downloading things from LCS you can be sure that you get the latest version that should be compatible with your other system.

Best regards,

Ludwig

Was this reply helpful? Yes No
Zen_Raj 177 on at

Like (0)

Report

RE: Electronic reporting - Error when importing XML configuration to another environment

Hi Ludwig,

It appears the original box is on 7.0.5314.35432 but the destination box is on 7.0.5314.35442. Is this absolutely necessary?

Thanks

Was this reply helpful? Yes No
Suggested answer

Ludwig Reinhard Microsoft Employee on at

Like (0)

Report

RE: Electronic reporting - Error when importing XML configuration to another environment

Hi,

Are both of your system on the same version and operate on the same PU?

Best regards,

Ludwig

Was this reply helpful? Yes No