cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
DA
Advocate III
Advocate III

CDS Update Record returns status 400

Trying to  update and existing record in a custom entity returns status 400: No resources were found when selecting for update

The Record with the given ID exits in the db.

1 ACCEPTED SOLUTION

Accepted Solutions

Hello DA,

 

Sorry for the delay. As a workaround can you please try to provide the value of PrimaryId field as the Record Id field input for the update action?

View solution in original post

16 REPLIES 16
v-monli-msft
Community Support
Community Support

Hi DA,

 

Please try to create a new flow with another new custom entity to test. If the issue disappear, take a screenshot of the detailed trigger and actions in this flow so that I would try to reproduce it.

 

Regards,

Mona Li

 

Community Support Team _ Mona Li
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Tried with a new custom entity and the standard entity contact. Both do not work.

Screenshot from the custom entity:

powerapp.PNG

 

Text output from the custom entity:

Eingaben

The database
default
The entity
MyContact
Record id
5637144576
Name
n1
Name2
b2

Ausgaben
Überschriften
{
"Pragma": "no-cache",
"x-dynint-corrid": "fcfd8b7a-d465-4f45-a1fb-6e625464edfb",
"x-dynint-userid": "09426fa9-dea9-42d8-a6cd-f62d2ce9f7fe",
"x-dynint-tenantid": "f761f78c-7d49-4d1b-b0ec-751b47c38741",
"x-dynint-namespaceid": "default",
"x-dynint-environmentid": "Default-f761f78c-7d49-4d1b-b0ec-751b47c38741",
"x-ms-client-request-id": "8802f7e2-6c87-40e4-a652-84326c7183b4",
"x-ms-correlation-request-id": "fcfd8b7a-d465-4f45-a1fb-6e625464edfb",
"x-dynint-service": "Connector",
"x-dynint-location": "West Europe",
"Strict-Transport-Security": "max-age=15724800; includeSubDomains",
"X-Content-Type-Options": "nosniff",
"Cache-Control": "no-cache",
"Date": "Fri, 04 Nov 2016 08:19:42 GMT",
"Server": "Microsoft-IIS/8.0,Microsoft-HTTPAPI/2.0",
"X-AspNet-Version": "4.0.30319",
"X-Powered-By": "ASP.NET",
"Content-Length": "116",
"Content-Type": "application/json; charset=utf-8",
"Expires": "-1"
}
Text
{
"status": 400,
"message": "No resources were found when selecting for update.",
"source": "rts-connector.powerapps.com"
}

 

Text output from the contact entity:

Eingaben

The database
default
The entity
Contact
Record id
5637144615
Full name
der tester
Party type
Organization
Source
Default
Is email contact allowed
true
Is phone contact allowed
false
Status
Active

Ausgaben
Überschriften
{
"Pragma": "no-cache",
"x-dynint-corrid": "b5b672cf-e810-4ac7-81c2-95b854526402",
"x-dynint-userid": "09426fa9-dea9-42d8-a6cd-f62d2ce9f7fe",
"x-dynint-tenantid": "f761f78c-7d49-4d1b-b0ec-751b47c38741",
"x-dynint-namespaceid": "default",
"x-dynint-environmentid": "Default-f761f78c-7d49-4d1b-b0ec-751b47c38741",
"x-ms-client-request-id": "78836be6-e678-4f1c-98b8-4b41ca8021fb",
"x-ms-correlation-request-id": "b5b672cf-e810-4ac7-81c2-95b854526402",
"x-dynint-service": "Connector",
"x-dynint-location": "West Europe",
"Strict-Transport-Security": "max-age=15724800; includeSubDomains",
"X-Content-Type-Options": "nosniff",
"Cache-Control": "no-cache",
"Date": "Fri, 04 Nov 2016 08:27:50 GMT",
"Server": "Microsoft-IIS/8.0,Microsoft-HTTPAPI/2.0",
"X-AspNet-Version": "4.0.30319",
"X-Powered-By": "ASP.NET",
"Content-Length": "116",
"Content-Type": "application/json; charset=utf-8",
"Expires": "-1"
}
Text
{
"status": 400,
"message": "No resources were found when selecting for update.",
"source": "rts-connector.powerapps.com"
}

 

DA
Advocate III
Advocate III

Any Updates. Tried this in an second enviroment. Same problem. The CDS Update is not working!

DA
Advocate III
Advocate III

Any Update? The CDS Update function is not working.

Tried with different environment -> same error.

Tried direct in Azure from a Logic App -> same error

DA
Advocate III
Advocate III

After 4  Weeks no answer and still not working.

 

And further problems:

DeleteRecord function returns the same error

SelectRecord returns error 404

 

Does not work in differnt environments, doses not work in Azure Logic APP

 

Could ba a great solution but not usebale a the moment.

 

The internal projects planed on CDS cannot be logner on hold. So we have to find a other Solution.

 

DA
Advocate III
Advocate III

We have opened a service call via Offie 365 2 weeks ago!

 

Same as here: No answer, no reaction

evel
Power Automate
Power Automate

Hi @DA

 

I wasn't able to reproduce your issue, and I've escalated your question to some folks who might be able to know more. Sorry about the long wait time. Hopefully we'll be able to work together to solve your issue. 

 

Thanks, 

-evel

Hello DA,

 

Sorry for the delay. As a workaround can you please try to provide the value of PrimaryId field as the Record Id field input for the update action?

View solution in original post

DA
Advocate III
Advocate III

Using the primary ID results in the same error 400

DA
Advocate III
Advocate III

manually entering the value of an exiting reords returns also error 400

Can you please share screenshots of your flow and also the MyContact entity fields? I am assuming you are trying to update MyContact entity record. Thanks

DA
Advocate III
Advocate III

I don't no if i missed somethig yesterday or something has changed.

 

I creadted a new Flow using the PrimaryId field as the Record Id and it is working.

 

So we can use this as workaround.

 

Usimg the ReordID filed as Record Id results still in the erros.

DA
Advocate III
Advocate III

The MyContact Entity was only for testing and is deleted.

At the moment i use the standard contact entity.

But i tested with diffrent entities and flows.

 

But as mentioned in my other post the workorund using the PrimaryId field as the Record Id seems to work.

 

 

Usimg the ReordID filed as Record Id results still in the erros.

 

I will setup an sync flow for one of our SQL Tables.

I will the post further feedback.

 

DA
Advocate III
Advocate III

Tested this with Standard and custom entity.

 

The workorund using the PrimaryId field as the Record Id is working.

 

The answer took so long because i ran in another isssue with lookup fileds adn the overall slow web interface at the moment

mcorning
Responsive Resident
Responsive Resident

I just found the same issue. screenshots follow.

 

Flow errorFlow error

CDS record to update (note correct RecordId)CDS record to update (note correct RecordId)

Strahlemann
Frequent Visitor

You can only use "CDS update record" when the key value, you are searching against, is actually defined as the Primary Key in the CDS Database settings.

Screen Shot 2017-11-14 at 15.26.50.png

Helpful resources

Announcements
UG GA Amplification 768x460.png

Launching new user group features

Learn how to create your own user groups today!

Community Connections 768x460.jpg

Community & How To Videos

Check out the new Power Platform Community Connections gallery!

Welcome Super Users.jpg

Super User Season 2

Congratulations, the new Super User Season 2 for 2021 has started!

Carousel 2021 Release Wave 2 Plan 768x460.jpg

2021 Release Wave 2 Plan

Power Platform release plan for the 2021 release wave 2 describes all new features releasing from October 2021 through March 2022.

Users online (2,022)