Forum Discussion
Error due to language settings when using Flows to provision libraries/lists on SharePoint
TuaRes-IT This problem is throughout the SharePoint REST API. For any collection object, be it Lists or Views or anything else, you get a choice of two methods: getByTitle(), which is dependent on the language of the user, and getByID or (guid'{guid}'), which is not portable between sites. It's a major flaw in that API, which has never been addressed, and the Graph API is better. It separates name and displayname better than the REST API.
TuaRes-IT This problem is throughout the SharePoint REST API. For any collection object, be it Lists or Views or anything else, you get a choice of two methods: getByTitle(), which is dependent on the language of the user, and getByID or (guid'{guid}'), which is not portable between sites. It's a major flaw in that API, which has never been addressed, and the Graph API is better. It separates name and displayname better than the REST API.
MartinLaplante Thank you Martin!
And as I was reading your post, I saw a link to an exposé by John Liu. As I see it, he proposes another way to add a new field of a list to a view: using the "AddToDefaultView'. Which, I guess, is 99% chance that it will be the "All items" view, whatever the language settings. Nice!