#NAME Error on Sharedpoint - How to make this work using Workspace or LSEG plugins?

NicolePangilinan

Client's query: I am using 3rd party API's now through a Microsoft Logic AppThe python tutorial was helpful, but a large learning curve.  My other subscription is working well.

The client is using Workspace. One example to share is data I am presenting through a MS Sharepoint page that won't update. A direct link to my spreadsheet does not have the LSEG plugins.

The screen shot below shows where I have a PDF of excel and the actual source excel. Top part is a linked PDF, below that is the link directly to the spreadsheet in Sharepoint with the errors #NAME?. This process forces me to open excel on my desktop and immediately export to the linked PDF each time.  It would be wonderful to have closing data each day automatically calculated through the excel or build the API updates inside Microsoft.

The client is now paying for another data service, unless you have a tutorial I could follow to build with LSEG. Not sure if this link is a starting place. https://developers.lseg.com/en/api-catalog/refinitiv-data-platform/refinitiv-data-platform-apis/documentation#esg-user-guide

Is it possible to link Workspace via Sharedpoint / Excel Online. Or other apps like Platform sessions? Please help clarifying workarounds that can satisfy client's requirements.

Thank you.

Jirapongse Phuriphanvichai

@NicolePangilinan

Thank you for reaching out to us.

I assume that the Excel file is a Workspace Excel file containing Workspace Excel formulas, such as =@RDP.Data. Workspace Excel files that rely on these formulas do not work in SharePoint or Excel Online, as they need to run locally with the Workspace Excel add-in which is available in the Workspace Excel application.

Although LSEG cloud services, such as the LSEG Data Platform, could provide a potential solution, the client would still need to develop and integrate the solution with SharePoint or Excel Online. If the client does not have SharePoint development experience, I believe the learning curve could be significantly steeper than learning Python.

In conclusion, the client should contact their LSEG account team or sales team directly to discuss this requirement. The team can recommend the most appropriate product or solution to meet the client's needs.