Microsoft Dynamics CRM (Archived)

Process->Set Properties got Error "Invalid Argument"

(1) Share

Report

Posted on by Community Member

Hi, I am creating an on-demand process on Plan object to update a field on itself.

When I click the 'set properties' button, I kept getting this error "Invalid Argument"

*This post is locked for comments

I have the same question (0)

All responses (10)

Answers (0)

Hosk on at

Like (0)

Report

You need to supply a bit more information

What type is the field and what value are you trying to update it with.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Basically, I want to manually run the workflow.

So I created a on-demand workflow and randomly picked the event for the workflow to be fired.

Then I picked the Primary object Plan as the object to be updated and clicked 'set properties' button. I got this error.

If I pick other objects such as 'Account', I am able to set properties.

Does this mean I can not update the primary object?

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hey TheHappyGiraff -

Did you ever solve this. If so do you know what fixed it?

I am having the exact same behavior but for me I am having the issue for the account entity. Like you I can easily create a workflow that updates or creates other entities but I cannot create a workflow that updates or creates an account. Seems like there must be something wrong in the account form.

When I create the workflow and choose to update an Account when I click the "set properties" I get the invalid argument just like you do.

Let me know if you figured it out.

Thanks

Hoss

Was this reply helpful? Yes No
Suggested answer

Community Member on at

Like (4)

Report

I got it solved for my environment.

I started a case with Microsoft and we did some detailed tracing and was able to capture that a certain field was throwing the invalid argument error. We removed that field from the form published and we still got the error but the traces showed a different field had the invalid argument issue.

Since this was a production system and we did not have a long downtime window the fix I used was. I saved the system managed account form as a new form. I then removed all of our custom fields from the system form. Made my new form the first form in the form order and then deactivated the original account form. Then I published and tried clicking set properties in workflow and it worked.

The workflow set properties looks to use the system account form as the form it uses to render and once I removed the offending fields which were impossible to figure out without the server traces, it all works.

Later

Hoss

Was this reply helpful? Yes No
Suggested answer

MRVIX 1,421 on at

Like (0)

Report

This worked for me! Thank you for sharing Hoss! You saved us haha :D

Was this reply helpful? Yes No
Saifudin 255 on at

Like (0)

Report

It worked for me too.

Thanks.

Was this reply helpful? Yes No
AlexMcL 8 on at

Like (0)

Report

Thanks Hoss, this worked for me (in my case for the Work Order entity).

I only needed to make the system form higher in the form order and publish, and I was able to set the properties in the workflow. [In my case in June 2020, I need to use a workflow as there are still things that flows don't support.]

Was this reply helpful? Yes No
RSalie 5 on at

Like (1)

Report

I got the same error today and noticed that the URL for the error contained some useful information - funny that this wasn't displayed on the page. The page just stated "Invalid argument".

I copied the URL (it has errorhandler.aspx in it), and replace %20 with a space to make it more readable. In between everything it stated "Error Details %3a Wrong type of attribute UI properties passed to attribute new_language".

Ordering of the forms fixed the issue.

Was this reply helpful? Yes No
OSB Cus Service AD 15 on at

Like (0)

Report

Hi every body !
I did what's written above, but it still didn't work for me...

I check the URL : "Expected%20non-empty%20string." OK !! But no information about the field concerned by the error...

I tried to switch main form with no result

I finally open a case to Microsoft and we modify the main form as below :

1) Create a new form and make it primary form

2) Take off the field "Createdon" + Save and publish

3) No more Invalid Argument !!

4) Put back the Createdon field + Save and Publish form => It works again !!

Createdon field was KO. + It may be another field that is Out of service => take off fields until it works !

Hope it helped you ;)

Romain

1 people found this reply helpful.

Was this reply helpful? Yes No
UllrSki 7 on at

Like (1)

Report

Adding to this solution...

I had the same issue but on a different field so I found this generic solution:

1) Create a new form and make it the primary form

2) Remove all non-required fields from the new form

3) Save and publish the form

4) In Power Apps, in your solution, set each of the other Main Forms to "Off"

5) Return to the Process > Workflow form and select "Set Properties" and make your modifications

4) In Power Apps, in your solution, set each of the other Main Forms to "On"

1 people found this reply helpful.

Was this reply helpful? Yes No