Excel add row function error

Rezah Zakiriah 1 Reputation point
2022-01-18T19:30:17.673+00:00

Hi All

I have a Logic App which writes to an excel template which is stored in a SharePoint location.
The template has a table which has columns. I had no issues with the app which ran fine for a period of time.
I am now receiving the error below.
I have tried removing the entire function and adding it back which works but by the next day the error is back and removes all the table parameters which I'm parsing through the function and replaces the table name with the string in the Table name parameter as can be seen in the second screen shot below.
I have also tried creating new connections on the function.

I am not sure why this seems to be happening as I have other Apps performing the same functions without any problem.

Excel Add row Function populated with all parameters

166153-image.png

Error received the next day

166077-image.png

Azure Logic Apps
Azure Logic Apps
An Azure service that automates the access and use of data across clouds without writing code.
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. Emily Hua-MSFT 27,866 Reputation points
    2022-01-19T02:43:11.363+00:00

    Hi @Rezah Zakiriah

    Welcome to Q&A forum ~

    I want to help you, but the tag "office-excel-itpro" focuses more on general issue of Excel client.
    Your issue is related to Power Automate, to help you better, I would suggest you post a new thread on following forum.
    Microsoft Power Automate Community

    Thanks for your understanding.


    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.



  2. MayankBargali-MSFT 70,981 Reputation points Moderator
    2022-01-20T12:37:12.64+00:00

    @Rezah Zakiriah Can you please confirm the second screenshot that you have shared is from the run history when your workflow is executed? As per the error looks like either the file is changed/modified which could have resulted in the exception that you have shared in your screenshot. Please verify if this is not the case and please confirm if any of the value location, document library, or file is dynamically specified in your workflow?

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.