Error while importing - CRM 2013 UR1 - Service request case associated with a contract / Invalid Argument

(0) Share

Report

Posted on by Tommy76

545

CRM 2013, update rollup 1 applied in Dev and QA environments (both). Same version. I exported a solution from the Dev environment, as a managed solution. I try to import the solution to the QA environment, and it fails with an error that seems absolutely irrelevant. The error message is "Service request case associated with a contract" and the Detail is "Invalid Argument". I don't use Service or Contract at all. I use the Case entity, which has been customized, and some web resources (javascript), but no Contract at all. Last week I did the same thing (export from Dev, import to QA), and it worked fine. I just fixed some bugs within javascript (web resources) but now I cannot import the solution again, because I always have this message. I tried to delete the managed solution from QA, but CRM don't let me delete the solution. Does anyone have an idea about what can be the problem (and a solution). One thing I'm pretty sure, is that the error message is probably irrelevant to the real problem (it's so frustrating!). One thing that has changed since the last export/import, is the Update Rollup 1 that has been installed on both environments. Otherwise I really don't see what could be the problem... Thanks!

*This post is locked for comments

I have the same question (0)

All responses (6)

Answers (0)

Suggested answer

rgoncalves on at

Like (0)

Report

It has no contract (even canceled) in the system?

Your javascript writes something in the database or affects fields in the database? Was it not deleted any record related to contracts??

Was this reply helpful? Yes No
Suggested answer

Hosk on at

Like (0)

Report

Often when I am having problems importing a solution it's because I have got a field with the same name but with different types

e.g.

new_field of type text

new_field of type whole number

have you made any changes to the fields, deleted a field and then recreated as a different type.

I believe this can occur when, you have a field in both environments (with the same schema name) but they are of different types.

Have you already customised the test environment? If so I would look to compare the custom fields on that entity.

Was this reply helpful? Yes No
Tommy76 545 on at

Like (0)

Report

Hi Ben. The only thing I did from a "field" perspective, is that I added a value in a listbox field (dev environment) to do some tests, then I removed the value so both fields in dev and QA are now the same. Other than that, I only updated some javascript code (OnSave event of the Case form). I also updated and disabled some business rules related to Case. But nothing related to contract. Thanks for your input.

Was this reply helpful? Yes No
Tommy76 545 on at

Like (0)

Report

I don't use Contracts at all in the system. The javascript validate some fields content and format the value, but nothing related to contracts. I discovered that when a field is business required, when you remove the value it doesn't trigger the OnChange event. When you update a value, the OnChange event is triggered. When the field is not business required, it works fine (when you remove a value and when you update a value). So to compensate this bug, I added some validation within the OnSave event to be sure that if Field A is empty and Field B has a specific value, an error message is displayed and the save is cancelled. This is basically what I have done, in addition to my other answer below. Thanks!

Was this reply helpful? Yes No
Luism 125 on at

Like (0)

Report

Dear Tommy,

Could you take a platform trace while you import the solution, and then open the trace and look for ": error"?

This should tell us what is the guid of the offending object, and this way we could go to the origin system, remove or correct the field, and then export the solution again.

Hopefully the import will succeed this way.

To create a trace you can follow these instructions:

support.microsoft.com/.../907490

Or use the CrmDiagTool, which creates those keys for you, although it's not Microsoft's app.

Kind regards

Was this reply helpful? Yes No
Marc Longtin on at

Like (0)

Report

HI LuisM,

I'M a colleague of Tommy. I enabled the tracing on the server and got the log files but the "error" doesn't tell us a whole lot. Can you contact me via email so I can forward you the logs for review. You can reach me at marc.longtin@acceo.com.

Thanks,

Was this reply helpful? Yes No