Skip to main content

I'm trying to use the new Microsoft Excel connector in NWC just released.

https://help.nintex.com/en-US/nwc/Content/Designer/Connectors/MicrosoftExcelConnector.htm 

 

In a sharepoint site I've created a document library. In the library I created a spreadsheet with an excel table. Table has two columns with headings and a single row of table data.

I've created an Excel connection in NWC.

 

When I use any of the actions for Microsoft excel. Nothing appears in the dropdown for workbook and I can't workout how to get the workbook ID.

 

I appreciate this is only version 1 of this connector and only released in the last week so the help documentation is very this at the moment on how to use and what the requirements are.

 

Any ideas friends?

Some small progress. I was able to see the excel file in the workbook dropdown when I stored the file in my onedrive.
However this is not a good solution for enterprises. Really needs to reference a sharepoint online document library.

Ok I've got this to work with a bit of trial and error.



I've also been using the microsoft graph api doco to try and work out the formatting



https://docs.microsoft.com/en-us/graph/api/table-post-rows?view=graph-rest-1.0&tabs=http 



Here is my excel sample file. This is stored in the root of my onedrive.



Note that I've created a grid with headers, formatted as table and then in the table design renamed the table to ResultsTable.





 



Next is a get table rows action.



 





 



I then use a count items in collection action to populate the RowCount integer variable.





I do some logging and looping just to see what the data looks like.



Next I do the insert table data action.



Note that row 1 of data in the table is actually row 0. So my RowCount variable is already number of rows plus 1 for the index position. So I can use the RowCount variable as the next row index to insert a new row into.



The rows and cells was a bit tricky to work out but here you can see how I inserted the last row of data as per the excel screenshot up top.



 





 



Hope this helps anyone else having try with this new connector.



 



And this really needs to be able to work with SharePoint Online document libraries and not files stored in OneDrive.


you are correct the connector only works with files stored in OneDrive.  


Hi everyone,



given the now confirmed limitation that the Excel connector is limited to OneDrive,



I've created a user voice request to extend the connector to work with SharePoint Online document libraries. 



Please give it a vote if you are after this functionality.



https://nintex.uservoice.com/forums/430063-5-nintex-workflow-cloud/suggestions/45025681-allow-the-microsoft-excel-connector-to-work-with-s 



 



Thanks,



Gavin


Is there any other settings or advice you can provide here on how to actually find or expose Excel files for use once you have the MS Excel connectors setup?

I have created the connection today using my personal O365 credentials, but I can't discern the logic or pattern that decides what Excel files are available to select when configuring the WF action. I can see two Excel files available, but neither are in my OneDrive root. If I put a new Excel file in the OneDrive root it isn't available.


Has anyone figured out what the workbook ID is and where to find it? 



 



I've setup the connection, created a form where the end user will upload the excel, the WF will then store the excel in OneDrive.  I need to use a variable to access the stored file but there are no instructions on how to identify the workbook ID...


Hey @TaniaS 



 



Check out the article I did detailing how we accomplished this with another user: https://jessemchargue.com/2022/05/10/use-case-extract-excel-data-in-nintex-workflow-cloud/



 



There is a download to the xtension I built out in the article as well. 


This is exactly what I needed, thanks so much!

Hey @jesse_mchargue,



 



Are you able to explain (in layman's terms) why the extension needs the User.Read.All permission to work? 



 



I don't have access to grant the permission so I'd like a little more info before I reach out to have the permission granted.



 



Cheers



Tania


Hey @TaniaS 



The User.Read.All allows for the app to read all of the profile properties of other users based on the signed-in user. This can be used for when you need to get additional details from other users than just the signed-in user.



 



Screenshot of the permissions from Azure:





 



User.ReadBasic.All may be enough, but it would be dependent on the scope of your use case. 


Reply