Character encoding in field names when working with power automate
This morning, I ran into an issue that I thought that someone else out there might run into. If you have a field name for example “SSL2” SharePoint is going to encode that field name with something like “_x0053_SL2″ you can see this name in the end of the URL when you open the list settings, then select that column. However, if you then try to use this field name in an OData filter you will get an error that the column does not exist. I was able to figure out that the field name when you are trying to access that field in the OData filter is “OData__x0053_SL2”. I was able to figure this out by creating a step that called Get Items without a filter then I checked the data that was returned.
Hope this helps someone!
This morning, I ran into an issue that I thought that someone else out there might run into. If you have a field name for example “SSL2” SharePoint is going to encode that field name with something like “_x0053_SL2” you can see this name in the end of the URL when you open the list settings, then select that column. However, if you then try to use this field name in an OData filter you will get an error that the column does not exist. I was able to figure out that the field name when you are trying to access that field in the OData filter is “OData__x0053_SL2”. I was able to figure this out by creating a step that called Get Items without a filter then I checked the data that was returned. Hope this helps someone! Read More