Customer experience | Sales, Customer Insights,...

Error Creating New Address

(0) Share

Report

Posted on by rdarrasUMed

When attempting to create a new address via Orders -> Lookup Address -> New address, I receive the error below. Does anyone know why this is happening and more importantly how to get rid of it.

Exception Message: An error occurred while validating input parameters: Microsoft.OData.ODataException: Cannot convert the literal '1' to the expected type 'Edm.String'. ---> Microsoft.OData.ODataException: Cannot convert a value of type 'Edm.Int32' to the expected target type 'Edm.String'.

Thanks in advance!

I have the same question (0)

All responses (8)

Answers (0)

Suggested answer

a33ik 84,331 Most Valuable Professional on at

Like (1)

Report

Hello,

That looks like a bug for me. I would recommend opening a ticket with Microsoft.

Was this reply helpful? Yes No
Ran Zhang on at

Like (0)

Report

Can you please share screenshot of how did you fill in the address? It looks like you were putting inconsistent type of value into the field.

Was this reply helpful? Yes No
rdarrasUMed 5 on at

Like (0)

Report

Ran Zhang, please see the screenshot below, I even added every single field that was not already on the form to make sure there wasn't a default value somewhere that was causing the issue.

Was this reply helpful? Yes No
rdarrasUMed 5 on at

Like (0)

Report

Thanks for the advice @andrew Butenko, I opened a request with my Gold Partner though I still haven't heard back from them yet.

Was this reply helpful? Yes No
Jacob.s17 464 on at

Like (0)

Report

It's telling you that it's looking for a string and you've provided an integer. Is the screenshot you shared the exact setup you used to generate the error? if yes, can you share more of your workflows details.

I had this identical error when trying to write a value to an option set in Power Automate earlier today, the issue was simply in how I provided the data for mapping. I know workflows aren't the same, but the error message is.

Anything else you can share?

Was this reply helpful? Yes No
rdarrasUMed 5 on at

Like (0)

Report

Seems like Andrew Butenko might be right about this being a bug. I was unaware until this morning there was an address table related to account and when I created an address from there, everything worked as expected. So there must be some sort of issue when attempting to create the same record via Orders -> Lookup Address -> New address

Was this reply helpful? Yes No
Frank Hillsnipe 1,332 on at

Like (0)

Report

Has anyone found a resolution to this?

The error appears to still exist in 2021 release wave 2.

Was this reply helpful? Yes No
Frank Hillsnipe 1,332 on at

Like (0)

Report

This is still an issue in 2022 release wave 2.

I did open a ticket with MS through my partner but it was not resolved and MS stopped responding about it.
The problem is that when you access the New Address form the Lookup Control and try to Save the Payload is incorrect and incomplete.

Failing Payload from Lookup Control:
{
"line1": "Test form Lookup",
"name": "Test from Lookup",
"objecttypecode": 1
}

Successful Payload from Account:
{
"line1": "Test from Account",
"name": "Test from Account",
"parentid_account@odata.bind": "/accounts(a9b26cd9-0fd8-eb11-a31a-0050568441e5)",
"objecttypecode": "account"
}

We see the error about the objecttypecode being 1 instead of Account (it would be 2 for a Contact or 4 for a Lead).
Additonally, it isn't submitting the parentid at all, fixing the objecttypecode and submitting it gets you a new error: "Parent id not set for address type 1071".

Was this reply helpful? Yes No