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

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Small and medium business | Business Central, N...
Unanswered

Update third party custom field error

(0) ShareShare
ReportReport
Posted on by

Hi expert,

we have created an extension A for D365BC, our partner also created an extension B for D365BC, then, our customer have an environment that have published both extension A and B to it. our customer want to write a cutom field named "test field" that exist in extension B not exust in extension A, this field exist in "Sales Line" table, below is my steps to accomplish that:

1. we already have a web service that named myService and its source table is "Sales Line"

2.Ask our partner to export sales line to a web service that include field "test field", named PartnerService

3. use myService to create a sales line.

4. use PartnerService to update sales line with field "test field" and http method is "patch"

when I export 20 items, sometims it will export successfully, sometimes it fails with 1 items successful, sometimes with 2 items successful, sometimes with 10 items successful, 

and it fails with different error, sometimes is "Another user has already changed the record.", sometimes is "Sorry, we just updated this page. Reopen it, and try again."

Any responses will be appreciated.

Thanks,

MIng

  • Community Member Profile Picture
    on at

    A few possibilities. The field may not have always have been required, or the field may not have always been present. So records could have existed in your DB either before this field was created, or after it was created and prior to it being set to required.

    2. Obviously all updates/changes of this account ( e.g. using integrated 3rd party software ) will trigger error ( all update trigger )... How to fix it?

    You have a few options. You can run a report of all records without this field populated and try to fill them in to ensure all your records have this field. You could also try to use a validation rule or some validation in your trigger itself, instead of making the field required at the field level. This way you can make the field required in certain scenarios and not required in other. I would suggest just trying to rectify the data issue (records without the field populated), rather than coding around it though.

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

Season of Sharing Community Challenge Winners!

Congratulations to our community stars!

Women in Power Builds Momentum

Expanding mentorship, skilling, and AI innovation

Leaderboard > Small and medium business | Business Central, NAV, RMS

#1
OussamaSabbouh Profile Picture

OussamaSabbouh 728 Super User 2026 Season 2

#2
YUN ZHU Profile Picture

YUN ZHU 545 Super User 2026 Season 2

#3
AndrewThomas81 Profile Picture

AndrewThomas81 328 Super User 2026 Season 2

Last 30 days Overall leaderboard

Featured topics

Microsoft Training Manuals

Product updates

Dynamics 365 release plans