web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Automate / Trigger SharePoint Whe...
Power Automate
Unanswered

Trigger SharePoint When a file is created/modified properties only is missing properties!

(1) ShareShare
ReportReport
Posted on by 104

I am using the trigger SharePoint - When a file is created or modified (properties only) and it appears to be missing properties at run time.

 

In the editor I see the properties I want to work with:

 

When it runs, the trigger doens't have the properties and the value doesn't show up in my further actions

 

Categories:
I have the same question (0)
  • wnzn Profile Picture
    168 on at

    I have encountered the same problem. On run time, a condition fails as the modified by appears to be NULL. When I click open the trigger (output used in condition), I see no mention of modified by or editor, only author. This Flow was working earlier. Something changed?

     

    Error i'm getting: 

    InvalidTemplate. Unable to process template language expressions for action 'Condition_-_Modified_by' at line '' and column '': 'The template language function 'endswith' expects its first parameter to be of type string. The provided value is of type 'Null'. 

  • wnzn Profile Picture
    168 on at

    Edit: this prevented my flows from going in an error state. However, the condition i set to check whether the item was modified by a service account (such as the one used in the flow) did not work anymore as the variable remained empty. This caused my flow to enter an endless loop. Created a ticket for this issue.

     

    As a workaround, I have added the initialize variable action as shown below before my condition and updated my condition to use the output variable 'Editor' from this action. Maybe this can be a temporary fix for you too. Would like to hear if something has changed in the backend that caused this issue to show up.

     

    workaround.png

  • v-xida-msft Profile Picture
    Microsoft Employee on at

    Hi @wnzn,

     

    Thanks for your feedback, the issue is confirmed on my side, I would post this issue to my product team. If the issue is solved, I would reply here.

     

    Best regards,

    Kris

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Users!

Kudos to our 2025 Community Spotlight Honorees

Congratulations to our 2025 community superstars!

Congratulations to the April Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Power Automate

#1
Vish WR Profile Picture

Vish WR 959

#2
Valantis Profile Picture

Valantis 872

#3
Haque Profile Picture

Haque 589

Last 30 days Overall leaderboard