property 'shared_office365' doesn't exist

[ChadVKealey]

It looks like this error is fairly common, but none of the "Solutions" out there are fixing it for me. I have a Flow, triggered by the "OnSelect" property of an icon in a PowerApp. The Flow creates an item in a list, then performs some other actions on that item (send email to the creator, starting an approval process, etc.). Originally, I had an O365 Users connection/action to get the first name ("Given Name") of the creator (to include in an email). When testing the flow, I was getting an error like this (the action mentioned was different, the rest of the message was the same). After removing the O365 Users action (Get my Profile (v2)), I'm still getting the same error, but now (as showen

Unable to process template language expressions in action 'Send_Submission_Notice_to_Student' inputs at line '1' and column '1967': 'The template language expression 'json(decodeBase64(triggerOutputs().headers['X-MS-APIM-Tokens']))['$connections']['shared_office365']['connectionId']' cannot be evaluated because property 'shared_office365' doesn't exist, available properties are 'shared_sharepointonline'. Please see https://aka.ms/logicexpressions for usage details.'.

I've gone as far as removing the O365 Users connection in the PowerApp and removing all remnants of it from the Flow. Still get the same message. I've re-linked the Flow to the icon a dozen times; no change. 

On a possibly related note, I noticed that this Flow seems to be listed as a "Logic flow" while another Flow linked in the same app does not show that designation (see below).

 

[Pieter_Veenstra · Accepted solution]

Hi @ChadVKealey,

There is an easy fix for this.

Export your flow.

Import your flow ( as a new flow).

Now the new flow will work.

this problem happens sometimes when you introduce new connectors to a flow after you have initially saved the flow without using that connector.

[GabrielStJohn]

Hello, @ChadVKealey!

Have you had an opportunity to apply @Pieter_Veenstra‘s recommendation to adapt your Flow? If yes, and you find that solution to be satisfactory, please go ahead and click “Accept as Solution” so that this thread will be marked for other users to easily identify! Thank you for being an active member of the Flow Community! 

-Gabriel

Flow Community Manager

[ChadVKealey]

Thanks, that did the trick, although it took me a couple of attempts to do it properly. 

I ran into the same issue with another flow in which I had never made a connection to "Office 365 Users", but where I had accidentally pasted a reference to it into the body in a "Send Email" action. It seems Flow is a bit touchy and there should be some kind of a "clean" function that can be run to delete any cached references or connections that are not used. Hopefully that will come as the product matures. It really kind of sucks to be running into issues like this and having to employ wacky workarounds with GA level applications.

[JenVitug]

@Pieter_Veenstra  THIS Is GREAT, IT worked  🙂 🙂 🙂  i've been trying to find a solution for this error for 3 days now.  Thank you so much 

[dimi]

Yes Pieter Veenstra his answer is indeed working (thank you!) but please, MS Flow team, elaborate on what, why ... or fix this issue because we can't keep spending time in such things and billing the customer for it ...

[DavePotts_BritE]

I've just tripped over this as well. I'm going to try the export-import solution.

Any Microsoft person looking able to comment on a more permenent fix for this?

[Pieter_Veenstra]

not rerunning a previous run should also work.

This means trigger the flow from a new triggering item, document or manual start.

[ChadVKealey]

If the Flow is triggered from a PowerApp (as most of mine are), removing the Flow as a data connection from the App, saving/publishing, then re-adding the Flow usually does the trick and is a lot simpler than exporting and importing the Flow.

[mo2]

Easiest fix, Turn off and on.

---

@ChadVKealey wrote:

It looks like this error is fairly common, but none of the "Solutions" out there are fixing it for me. I have a Flow, triggered by the "OnSelect" property of an icon in a PowerApp. The Flow creates an item in a list, then performs some other actions on that item (send email to the creator, starting an approval process, etc.). Originally, I had an O365 Users connection/action to get the first name ("Given Name") of the creator (to include in an email). When testing the flow, I was getting an error like this (the action mentioned was different, the rest of the message was the same). After removing the O365 Users action (Get my Profile (v2)), I'm still getting the same error, but now (as showen

Unable to process template language expressions in action 'Send_Submission_Notice_to_Student' inputs at line '1' and column '1967': 'The template language expression 'json(decodeBase64(triggerOutputs().headers['X-MS-APIM-Tokens']))['$connections']['shared_office365']['connectionId']' cannot be evaluated because property 'shared_office365' doesn't exist, available properties are 'shared_sharepointonline'. Please see https://aka.ms/logicexpressions for usage details.'.

I've gone as far as removing the O365 Users connection in the PowerApp and removing all remnants of it from the Flow. Still get the same message. I've re-linked the Flow to the icon a dozen times; no change. 

On a possibly related note, I noticed that this Flow seems to be listed as a "Logic flow" while another Flow linked in the same app does not show that designation (see below).

 

---

[abecerra]

Yes! This work as well as when you are having other flow errors that you can't pin point where it can be failing. Two days wasted on this!

[casepilots]

This also worked for me so thanks for that. In my case it was a Dynamics 365 connection.

[Anonymous]

---

@Pieter_Veenstra wrote:
not rerunning a previous run should also work.

This means trigger the flow from a new triggering item, document or manual start.

---

This worked for me and I didn't have to do the export/import. Thanks!

[Rodolfo1840]

It worked on my side

[Gabriel_CMET]

Hi Pieter,

my problem is, this happens with all my Powerapps triggered flows and every time i ad/change  a sharepoint action. Do you think i messed something up with my connectors?

Thanks,

[ChadVKealey]

It seems there is a maximum number of instances of a connection. For example, a single SharePoint connection can only be used a certain number of times in apps or flows. I don't know what the actual number is, but the Power Apps folks at Ignite last year told me that's why I had 3 SharePoint connections (basically, I 'used up' two of them, so had to create a new one).

When you go to your flow, rather than selecting the existing SharePoint connection, click "Add new". 

This can surface weirdly because when you open an App, if you used two different SharePoint connectors (tied to the same account), you see the "SharePoint" permissions notice twice. 

[Anonymous]

@Pieter_Veenstra .....what a life saver you are! THANK YOU! And the few hairs that I have left after the past 3 hours THANK YOU too! lol

[cvss]

This solution works for me. Thank you!

[Eclectic211]

This fixed my issue, thank you Pieter.

[JColvin]

This is not a solution, this is a workaround. Microsoft needs to address the root cause on this, as it continues to cause hours upon hours of lost time. I have been fighting this error regularly for 3 years.