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 :
Microsoft Dynamics CRM (Archived)

doesn't Xrm.Webapi support custom fields?!

(0) ShareShare
ReportReport
Posted on by 1,030

why do I get this:

Default Price List: Could not find a property named 'new_worldterritoryid' on type 'Microsoft.Dynamics.CRM.account'.

...from this:

    this.determineDefaultPxLst = function (ExecutionContext, accountid) {
        formContext = ExecutionContext.getFormContext();
        Xrm.WebApi.retrieveRecord("account", accountid, "?$select=name&$expand=new_worldterritoryid($select=_new_defaultpricelevelid_value)").then(

And, yes, it's there.  Has been for months.

*This post is locked for comments

I have the same question (0)
  • Martin Donnelly Profile Picture
    1,030 on at
    RE: doesn't Xrm.Webapi support custom fields?!

    ...and now I've tried Xrm.WebApi.retrieveMultipleRecords(... with fetchXML and it won't come out.  The same fetch that works with advanced find and fetch tester yields a count of 1 but no worldterritoryid.

    I give up.

  • Martin Donnelly Profile Picture
    1,030 on at
    RE: doesn't Xrm.Webapi support custom fields?!

    Can't explain why the fetchXML doesn't work but discovered the web api query string requires schema name, new_WorldTerritoryId.

  • Kokulan Profile Picture
    18,054 on at
    RE: doesn't Xrm.Webapi support custom fields?!

    If you would like to explore this further to see why the FETCH did not work, please share the code

  • Suggested answer
    Aric Levin - MVP Profile Picture
    30,190 Moderator on at
    RE: doesn't Xrm.Webapi support custom fields?!

    There shouldn't be any reason why you can't find your property.

    Try using CRM Rest Builder (version 2.6) and generate you WebApi function call.

    This will show you what is missing.

    Hope this helps.

  • Verified answer
    MSCRM Guru Profile Picture
    600 on at
    RE: doesn't Xrm.Webapi support custom fields?!

    Hi mardukes,

    I've found in the past that the WebAPI can be case sensitive for entity and attribute names - really depends on the specific version you are working with.  Basically if the schema name of your attribute is new_WorldTerritoryId, new_WorldTerritoryid, new_WorldterritoryId, etc. it wont work as expected.

    Try copy\pasting the attribute schema name from the solution.

    Hope that makes sense and resolves it.

    Good luck!

  • Martin Donnelly Profile Picture
    1,030 on at
    RE: doesn't Xrm.Webapi support custom fields?!

    Yes, I recalled this from the SOAP days and decided to give it a try.

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

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Abhilash Warrier – Community Spotlight

We are honored to recognize Abhilash Warrier as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics CRM (Archived)

#1
HR-09070029-0 Profile Picture

HR-09070029-0 2

#1
UllrSki Profile Picture

UllrSki 2

#3
ED-30091530-0 Profile Picture

ED-30091530-0 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans