Showing results for 
Search instead for 
Did you mean: 
Responsive Resident
Responsive Resident

Problem with Create a new record from Common Data Service (current environment) connector

Hi All,

I was trying to use the Create a new record action from the new connector and am getting an error whenever trying to add a relationship value.

For example, when adding a new Expense that has a lookup field to Currency.  When I supply the CurrencyId (GUID) to the field of the Expense I get an error:

"code": "0x0",
"message": "Resource not found for the segment '[MY_GUID]'.",

Where [MY_GUID] is the actual Id.  This happens for every type of field that is a relationship.  If I use the old Common Data Service "Create a new record" action it works just fine.


Accepted Solutions
Advocate I
Advocate I

After some investigation of what's going on behind the scenes in comparison to the regular Common Data Service connector I saw that previously 

"item/_transactioncurrencyid_value" : "YOUR_GUID"

was used to populate the lookup in the API call, this requiring only the GUID of the currency to be filled in as a parameter in Flow. Now with the current environment this changed to

"item/TransactionCurrencyId@odata.bind": "/transactioncurrencies(YOUR_GUID)"

Sadly, at the moment the "/transactioncurrencies(" and ")" are not added to the API call when you simple add a GUID field as parameter for your action. So, the solution for now (expecting this to be solved as a bug soon), is to manually add these two parts in your lookup field to make the API call valid.


View solution in original post

Solution Sage
Solution Sage

Hi @Helpful ,

Could you please share a screenshot of your flow's configuration?

As you said when you Created a new record with the new connection, the error occurred.

So please make sure the new connection has the permission to the entity you want.

Best Regards,

Community Support Team _ Zhongys

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Thanks, @v-zhos-msft,

I have since reconfigured to use the existing CDS "Create a new record" action.  In my post I was referring to the new CDS connector called "Common Data Service (current environment)".  Announced here:

I used that connector for the Trigger event, as well as a Get record action in the Flow, however, when it came time to Create a record it got wierd.

I'm not going to spend too much time on it because the info seems pretty limited.  Even the documentation link in that anouncement goes to a 404 page.

Advocate I
Advocate I

After some investigation of what's going on behind the scenes in comparison to the regular Common Data Service connector I saw that previously 

"item/_transactioncurrencyid_value" : "YOUR_GUID"

was used to populate the lookup in the API call, this requiring only the GUID of the currency to be filled in as a parameter in Flow. Now with the current environment this changed to

"item/TransactionCurrencyId@odata.bind": "/transactioncurrencies(YOUR_GUID)"

Sadly, at the moment the "/transactioncurrencies(" and ")" are not added to the API call when you simple add a GUID field as parameter for your action. So, the solution for now (expecting this to be solved as a bug soon), is to manually add these two parts in your lookup field to make the API call valid.


Responsive Resident
Responsive Resident

Bravo!  Just got back from vacation, tried this and it works as you spec'd.

Sadly, this means my Create action will break as soon as the bug is fixed, but this gets me using a single connection type for the flow.  Much appreciated.

I'm chiming in on this thread as I've been going over the issue myself, with other MVPs and with the product team. This is currently by design. The CDS (current environemnt) connector expects the referenced attribute values in the form of OData id (entity-name(record-id)).


I realize digging for the entity names may sometimes be a bit of work, especially as core CE, PSA and FS have differences in how entities are named. There is a way to dig out an entity name from a "Get records" action to hopefully help with this a bit. I'm working on a post around this and will update this thread with a link in the near future.


Check out my Project Operations and Power Automate blog at:

Thanks for the video. It was really helpful. 


So the MS product team confirmed that the annoying additional step to create a compose is by design and they won't be changing it? 


That's a bit disappointing since I was looking forward to using the new CDS connector but this one area seems to be a downgrade.

This "feature" makes the connector unusable for us.  We have flows where we reference 10 other records or more.  Now, when the referenced GUID is blank on a particular record, instead of writing a null value in the flow with all other steps executing properly,  the flow fails because the syntax is incorrect for that one null value.   We've spent quite a bit of time trying workaround expressions- "if(empty(outputs....." and have been unable to make anything work. 

I completely agree. It's really stupid. There are times where I might not have a GUID value for that specific field but I'm forced to add in the entity reference. 

This was raised as an issue. Please up vote for quicker resolution.







I am also facing issue while creating Project task record.


Thanks in advanced.


Regular Visitor

Try the expression

concat('projects(',triggerOutputs()?['body/_msdyn_project_value'], ')')

Regular Visitor

I have a problem creating a new record in that the contact GUID that I pass is not being accepted. I get this error: Resource not found for the segment '6a93486d-9809-eb11-a813-000d3a569ac4'. I know the GUID is correct because I can paste in a URL and it loads the correct Contact in Dynamics.  Here is a peak at the source in the Create Record Action: 

    "inputs": {
        "host": {
        "parameters": {
            "item/title""@{triggerBody()['text']} @{triggerBody()['text_1']}",


With the new connector, the required syntax is ‘Contacts(GUID)’

just sending the GUID won’t work, you need to add the plural schema name of the entity plus () with the GUID inside

Thankyou Captjoemcd


I made the change to use 'Contacts(@{items('Apply_to_each')?['contactid']})' but I get this error -> Bad Request - Error in query syntax.


But contacts(@{items('Apply_to_each')?['contactid']}) works, so it appears case sensitive. ie contacts(GUID) works


Thanks much for your help.


Responsive Resident
Responsive Resident

Still working with this as designed and still not liking it.

I'm sure there's a good reason for putting Flow authors through these extra steps, but it's not clear what it is from an outside perspective.

Take an example of using a Flow to copy a record.  It involves creating a new record with potentially several relationships that may or may not have values.

Each relationship field on the new record has to have an expression (to determine if it exists) that includes the relationship prefix and the funky '_value' string... kind of a mess for a very common scenario.

I'm sure everyone has their syntax for the expression that handles empty relationship values figured out, but thought I'd add it to the thread.  Below is an example of an expression added to a relationship field of of a "Create new record" action where I'm looping through records and creating copy of each one.



if(empty(items('For_each_Child_Record')?['_xyz_relatedrecordid_value']), '', concat('/relatedrecords(',items('For_each_Child_Record')?['_xyz_relatedrecordid_value'],')'))



Helpful resources


Win free tickets to the Power Platform Conference | Summer of Solutions

We are excited to announce the Summer of Solutions Challenge!    This challenge is kicking off on Monday, June 17th and will run for (4) weeks.  The challenge is open to all Power Platform (Power Apps, Power Automate, Copilot Studio & Power Pages) community members. We invite you to participate in a quest to provide solutions to as many questions as you can. Answers can be provided in all the communities.    Entry Period: This Challenge will consist of four weekly Entry Periods as follows (each an “Entry Period”)   - 12:00 a.m. PT on June 17, 2024 – 11:59 p.m. PT on June 23, 2024 - 12:00 a.m. PT on June 24, 2024 – 11:59 p.m. PT on June 30, 2024 - 12:00 a.m. PT on July 1, 2024 – 11:59 p.m. PT on July 7, 2024 - 12:00 a.m. PT on July 8, 2024 – 11:59 p.m. PT on July 14, 2024   Entries will be eligible for the Entry Period in which they are received and will not carryover to subsequent weekly entry periods.  You must enter into each weekly Entry Period separately.   How to Enter: We invite you to participate in a quest to provide "Accepted Solutions" to as many questions as you can. Answers can be provided in all the communities. Users must provide a solution which can be an “Accepted Solution” in the Forums in all of the communities and there are no limits to the number of “Accepted Solutions” that a member can provide for entries in this challenge, but each entry must be substantially unique and different.    Winner Selection and Prizes: At the end of each week, we will list the top ten (10) Community users which will consist of: 5 Community Members & 5 Super Users and they will advance to the final drawing. We will post each week in the News & Announcements the top 10 Solution providers.  At the end of the challenge, we will add all of the top 10 weekly names and enter them into a random drawing.  Then we will randomly select ten (10) winners (5 Community Members & 5 Super Users) from among all eligible entrants received across all weekly Entry Periods to receive the prize listed below. If a winner declines, we will draw again at random for the next winner.  A user will only be able to win once overall. If they are drawn multiple times, another user will be drawn at random.  Individuals will be contacted before the announcement with the opportunity to claim or deny the prize.  Once all of the winners have been notified, we will post in the News & Announcements of each community with the list of winners.   Each winner will receive one (1) Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value). NOTE: Prize is for conference attendance only and any other costs such as airfare, lodging, transportation, and food are the sole responsibility of the winner. Tickets are not transferable to any other party or to next year’s event.   ** PLEASE SEE THE ATTACHED RULES for this CHALLENGE**

Celebrating the June Super User of the Month: Markus Franz

Markus Franz is a phenomenal contributor to the Power Apps Community. Super Users like Markus inspire others through their example, encouragement, and active participation.    The Why: "I do this to help others achieve what they are trying to do. As a total beginner back then without IT background I know how overwhelming things can be, so I decided to jump in and help others. I also do this to keep progressing and learning myself." Thank you, Markus Franz, for your outstanding work! Keep inspiring others and making a difference in the community! 🎉  Keep up the fantastic work! 👏👏 Markus Franz | LinkedIn  Power Apps: mmbr1606  

Copilot Cookbook Challenge | Week 1 Results | Win Tickets to the Power Platform Conference

We are excited to announce the "The Copilot Cookbook Community Challenge is a great way to showcase your creativity and connect with others. Plus, you could win tickets to the Power Platform Community Conference in Las Vegas in September 2024 as an amazing bonus.   Two ways to enter: 1. Copilot Studio Cookbook Gallery: 2. Power Apps Copilot Cookbook Gallery:   There will be 5 chances to qualify for the final drawing: Early Bird Entries: March 1 - June 2Week 1: June 3 - June 9Week 2: June 10 - June 16Week 3: June 17 - June 23Week 4: June 24 - June 30     At the end of each week, we will draw 5 random names from every user who has posted a qualifying Copilot Studio template, sample or demo in the Copilot Studio Cookbook or a qualifying Power Apps Copilot sample or demo in the Power Apps Copilot Cookbook. Users who are not drawn in a given week will be added to the pool for the next week. Users can qualify more than once, but no more than once per week. Four winners will be drawn at random from the total qualifying entrants. If a winner declines, we will draw again at random for the next winner.  A user will only be able to win once. If they are drawn multiple times, another user will be drawn at random. Prizes:  One Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value, does not include travel, lodging, or any other expenses) Winners are also eligible to do a 10-minute presentation of their demo or solution in a community solutions showcase at the event. To qualify for the drawing, templates, samples or demos must be related to Copilot Studio or a Copilot feature of Power Apps, Power Automate, or Power Pages, and must demonstrate or solve a complete unique and useful business or technical problem. Power Automate and Power Pagers posts should be added to the Power Apps Cookbook. Final determination of qualifying entries is at the sole discretion of Microsoft. Weekly updates and the Final random winners will be posted in the News & Announcements section in the communities on July 29th, 2024. Did you submit entries early?  Early Bird Entries March 1 - June 2:  If you posted something in the "early bird" time frame complete this form: if you would like to be entered in the challenge.   Week 1 Results:  Congratulations to the Week 1 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Copilot Cookbook Gallery:Power Apps Cookbook Gallery:1.  @Mathieu_Paris 1.   @SpongYe 2.  @Dhanush 2.   @Deenuji 3.  n/a3.   @Nived_Nambiar  4.  n/a4.   @ManishSolanki 5.  n/a5.    n/a

Your Moment to Shine: 2024 PPCC’s Got Power Awards Show

For the third year, we invite you, our talented community members, to participate in the grand 2024 Power Platform Community Conference's Got Power Awards. This event is your opportunity to showcase solutions that make a significant business impact, highlight extensive use of Power Platform products, demonstrate good governance, or tell an inspirational story. Share your success stories, inspire your peers, and show off some hidden talents.  This is your time to shine and bring your creations into the spotlight!  Make your mark, inspire others and leave a lasting impression. Sign up today for a chance to showcase your solution and win the coveted 2024 PPCC’s Got Power Award. This year we have three categories for you to participate in: Technical Solution Demo, Storytelling, and Hidden Talent.      The Technical solution demo category showcases your applications, automated workflows, copilot agentic experiences, web pages, AI capabilities, dashboards, and/or more. We want to see your most impactful Power Platform solutions!  The Storytelling category is where you can share your inspiring story, and the Hidden Talent category is where your talents (such as singing, dancing, jump roping, etc.) can shine! Submission Details:  Fill out the submission form by July 12th with details and a 2–5-minute video showcasing your Solution impact. (Please let us know you're coming to PPCC, too!)After review by a panel of Microsoft judges, the top storytellers will be invited to present a virtual demo presentation to the judges during early August. You’ll be notified soon after if you have been selected as a finalist to share your story live at PPCC’s Got Power!  The live show will feature the solution demos and storytelling talents of the top contestants, winner announcements, and the opportunity to network with your community.  It's not just a showcase for technical talent and storytelling showmanship, show it's a golden opportunity to make connections and celebrate our Community together! Let's make this a memorable event! See you there!   Mark your calendars! Date and Time: Thursday, Sept 19th Location: PPCC24 at the MGM Grand, Las Vegas, NV 

Tuesday Tip | Accepting Solutions

It's time for another TUESDAY TIPS, your weekly connection with the most insightful tips and tricks that empower both newcomers and veterans in the Power Platform Community! Every Tuesday, we bring you a curated selection of the finest advice, distilled from the resources and tools in the Community. Whether you’re a seasoned member or just getting started, Tuesday Tips are the perfect compass guiding you across the dynamic landscape of the Power Platform Community.   To enhance our collaborative environment, it's important to acknowledge when your question has been answered satisfactorily. Here's a quick guide on how to accept a solution to your questions: Find the Helpful Reply: Navigate to the reply that has effectively answered your question.Accept as Solution: Look for the "Accept as Solution" button or link, usually located at the bottom of the reply.Confirm Your Selection: Clicking this button may prompt you for confirmation. Go ahead and confirm that this is indeed the solution.Acknowledgment: Once accepted, the reply will be highlighted, and the original post will be marked as "Solved". This helps other community members find the same solution quickly. By marking a reply as an accepted solution, you not only thank the person who helped you but also make it easier for others with similar questions to find answers. Let's continue to support each other by recognizing helpful contributions. 

Reminder: To register for the Community Ambassador Call on June 13th

Calling all Super Users & User Group Leaders   Reminder: To register for the Community Ambassador Call on June 13th—for an exclusive event for User Group Leaders and Super Users! This month is packed with exciting updates and activities within our community.   What's Happening: Community Updates: We'll share the latest developments and what's new in our vibrant community.Special Guest Speaker: Get ready for an insightful talk and live demo of Microsoft Copilot Studio templates by our special guest.Regular Updates: Stay informed with our routine updates for User Groups and Super Users.Community Insights: We'll provide general information about ongoing and upcoming community initiatives. Don't Miss Out: Register Now: Choose the session that fits your schedule best.Check your private messages or Super User Forum for registration links. We're excited to connect with you and continue building a stronger community together.   See you at the call!  

Users online (3,031)