You’re offline. This is a read only version of the page.
Announcements
258
I'm using the SharePoint HTTP Request action to add orders to a table.
For reasons unknown, columns LOT1, LOT2, and LOT3 were secretly given the internal names _x004c_OT1, _x004c_OT2, and _x004c_OT3 when I was creating them. This is fine, but for some reason I can't reference these columns by their display name or internal name when building batch requests, since I'll get an error that LOT1 or _x004c_OT1 doesn't exist, depending on the one I'm trying to use.
This is how I'm referencing them in the changesets:
As a test, I tried making a new column, HOT1 (which got an internal name of _x0048_OT1), and using that where LOT1 was referenced, but it gave me the same error, so it looks like deleting and remaking the LOT columns won't fix it. What do I do in this case? I'm trying to avoid giving the columns new names, since this is intended to mirror another database.
Hi @bobesponja,
When the internal name starts with an underscore Microsoft typically adds OData in front of it. Have a look at this blog:
Try something like:
OData_x004c_OT1
Share
Report
All responses (
Answers (
