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

Community site session details

Session Id : c/GaLLq74qrXscEEbdLJTb
Power Automate - Building Flows
Unanswered

"Resource not found for the segment" error, all solutions on the forum tried

Like (0) ShareShare
ReportReport
Posted on 2 Nov 2020 12:57:25 by 232

When I try a simple flow to create records after a record created I get a "Resource not found for the segment" error.

 

Screenshot 2020-11-02 at 12.40.09.png

 

I've tried all the options suggested elsewhere.

 

Clients(GUID)

/Clients(GUID)

/Clients/GUID

GUID

 

I also tried c9_memberships(GUID) (which is the field name)

Screenshot 2020-11-02 at 12.37.27.png

GUID on it's own, and c9_memberships(GUID) returns the error "Resource not found for the segment 'f5e89b62-36d9-e911-a813-000d3a86d655'."

all the others return the error "Resource not found for the segment 'Clients'.)

 

I get this for both the standard Common Data Service trigger, and the Common Data Service (Current Environment) trigger.

 

Shouldn't this just work with the GUID?

 

Any suggestions?

  • MJain Profile Picture
    2,450 on 02 Nov 2020 at 14:08:33
    Re: "Resource not found for the segment" error, all solutions on the forum tried

    Hi @mrpowergage ,

     

    Just to update plural name highlighted is not schema name whereas c9_membership is . 

     

    Thanks

     

  • mrpowergage Profile Picture
    232 on 02 Nov 2020 at 14:06:56
    Re: "Resource not found for the segment" error, all solutions on the forum tried

    Thanks, but I'm pretty sure I am:

     

    Screenshot 2020-11-02 at 14.05.24.png

     

    I'm recreating the flow from scratch using the standard CDS trigger, and that seems to be doing the trick.

  • MJain Profile Picture
    2,450 on 02 Nov 2020 at 13:22:51
    Re: "Resource not found for the segment" error, all solutions on the forum tried

    Hi @mrpowergage ,

     

    In order to refer to lookup value you should be using plural schema name of entity and not display name.  Look for your customization prefix of entity and use it , eg. new_clients .

     

    https://docs.microsoft.com/en-us/powerapps/developer/common-data-service/webapi/create-entity-web-api

     

    http://linnzawwin.blogspot.com/2019/11/power-automate-how-to-set-lookup-field.html

     

     

    Thanks

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

Announcing our 2025 Season 2 Super Users!

A new season of Super Users has arrived, and we are so grateful for…

Paul Stork – Community Spotlight

We are honored to recognize Paul Stork as our July 2025 Community…

Congratulations to the June Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Power Automate

#1
Michael E. Gernaey Profile Picture

Michael E. Gernaey 497 Super User 2025 Season 2

#2
David_MA Profile Picture

David_MA 436 Super User 2025 Season 2

#3
Riyaz_riz11 Profile Picture

Riyaz_riz11 244 Super User 2025 Season 2

Loading complete