Automatic flow not detecting page creation

(0) Share

Report

Posted on by EZSULD

Hi all.

I have a strange issue with one of my power automate flows.

I've created a type of handover system that works as follows:

- Sharepoint page template is used to write a handover.

- The URL of the handover uses a naming convention (RDCC).

- PA flow scans for page creation within site pages, any page that has RDCC in the title.

- Moves RDCC handovers to folder.

The flow seems to work fine when I create the pages, but doesn't seem to pick up others that create the page, using the same template, steps, and naming convention.

More screenshots available if needed, as I can only attach 3x I did not include the compose action.

The input is body/title from the initial action.

Categories:

Business Process Flows

RDCC3.JPG

RDCC1.JPG

RDCC4.JPG

I have the same question (0)

All responses (2)

Answers (0)

Expiscornovus 33,175 Most Valuable Professional on at

Like (0)

Report

Automatic flow not detecting page creation

HI @EZSULD,

Are you using a trigger condition with the Title in the When a file is created (properties only) trigger action?

If so, can you share that as well?

What could happen is that somebody creates the page and autosave kicks in before the Title has been added by the author. The first autosave will create the aspx page and will trigger the flow.

In that case the title would be empty when the file is created (see screenshot below). If you are using a trigger condition with the Title the flow would never be triggered.

For this reason I have used the when a file is modified trigger action instead and used a trigger condition expression to check when a page was published instead (when it has all the details).

Was this reply helpful? Yes No
EZSULD 7 on at

Like (2)

Report

Automatic flow not detecting page creation

Hi @Expiscornovus

Thank you for getting back to me.

I don't fully understand what you're trying to say, but I think I get the gist of it.

After making the post I changed the trigger to be "When a file is created or modified (properties only)" with the same config as before.

I think that the autosave issues you mention may have thrown it off slightly, and the inclusion of "modified" to the trigger should capture any further issues with the pages.

I've expanded the advanced parameters also so you can see, and the compose action is not really needed.

I have three copies of this flow with different naming conventions, for different handovers, and this seems to have fixed the issue with all.

This does seem to have solved the issue, I've tested with 3x team members that WFH (and don't touch the flows) and it managed to locate and move correctly.

Was this reply helpful? Yes No