I have a flow that I co-own with a coworker. Both of our Sharepoint and Outlook 365 accounts are added as connections for this flow. The flow's purpose is to take items from a Sharepoint list, filter them, create an HTML table, and then email the table from my coworker's email account. Two errors repeatedly occur that I cannot resolve.
The first: whenever a change is made to the flow, the Create HTML Table will fail on the next run, citing that the columns do not exist. I have to recreate the table everytime I change something in the flow to avoid this.
The second: The email cannot be sent from my coworker's email address. If the From: option is left blank, it works well and send from my email account, however it will not send from my coworker's. This flow was created in her account, and then later edited by me. I have tried logging into her account to add her email address, and also tried creating the 'Send email' function while logged in as her, I still receive the same error: You are not allowed to send emails from this account. I am looking at having to recreate the entire flow in her account to see if this resolved the problem.
Are there any other solutions to these problems, short of constantly recreating the flow or HTML tables when I need to make a change, as that can quickly become time consuming? Thank you for your help.
If you change the column in the list, then Create HTML table will definitely be affected. In general, as long as the column of the list is changed, many action involving the column will have an error because the request sent cannot be responded.
It seems that you could only do no custom configuration of Create Html table-Columns, so no matter how the list is changed, it will not affect the action.
Do you mean that this error occurs when populating email address in From?
This seems to involve the issue of permission configuration, please refer to this link:
Thank you for the information. With regards to the HTML tables, it is not when I make a change to the list that it fails, but when I make a change to the flow. For example, my flow is set up: Get items -> Filter array -> Create HTML table -> Send Email. If I make any change to the flow, such as changing the wording of the email that will be sent, I have to recreate the 'Create HTML table' step or else it will fail on my next run. The error I receive is that one of the columns, say Column A, cannot be found and the table cannot be created. If I delete and re-add the dynamic content of Column A to the HTML table, then the next time it will fail and cite another column, Column B, does not exist. This will continue until the dynamic content of all columns on the table is deleted and re-added. To save time and runs, I have to delete all dynamic content from the 'Create HTML Table' step and then readd it whenever I make any change to the flow. Is this just part of having a custom HTML table in my flow, or is there another way around this issue?
As to the second issue, it appears that all steps leading up to the 'Send email step' have to be created by the owner whose email address the email will be sent from, regardless of what connections are added to the flow. So, with the above flow as an example, if my coworker creates the flow to say Get items ->Create HTML table -> Send email, then the flow can send the email from her email address. If I then go in under my account and alter to flow to say Get items -> Filter array -> Create HTML table -> Send email, then we receive the error that the flow does not have permission to send from my coworkers email account. To workaround this, we have to recreate the flow so that all the steps are created by my coworker. Is that a correct assumption to make? Thank you for the help!
Is there any update to this? My 'Create HTML table' step still fails repeatedly when I do not make changes to the list, only minor changes to the flow. If there is a way to fix this, I would appreciate it, as I now have five different HTML tables in this flow, and recreating them for every minor change in wording an email is time consuming. Thank you!