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 :
Dynamics 365 Community / Forums / Business Central forum / The Multi-part Identif...
Business Central forum

The Multi-part Identifier "xxxxxx.field" could not be bound. in BC on-premises when we search on list page which has a custom field.

(1) ShareShare
ReportReport
Posted on by Ramesh G 97

Is there anybody experiencing the below error in Business central on premises.

error  "The Multi-part Identifier 'xxxxxx.field' could not be bound" comes when we search on list page which has a custom field.

ref:

pastedimage1565183919729v1.png

custom field added on table extension and as well in page extension.

how to fix it.

Categories:
Other
  • Suresh Kulla Profile Picture
    Suresh Kulla 50,280 Super User 2026 Season 1 on at

    Is that field a flowfield? this was reported earlier but fixed. What version are you using? maybe check the Calcformulae

    github.com/.../509

  • Ramesh G Profile Picture
    Ramesh G 97 on at

    it is not flow field yet, its a custom field in table extension field type is Code[20}

    and its coming in web client only.

  • Suggested answer
    Suresh Kulla Profile Picture
    Suresh Kulla 50,280 Super User 2026 Season 1 on at

    Does it have a table relation property set? it is working on the web client but not on the Win Client?

  • Ramesh G Profile Picture
    Ramesh G 97 on at

    the error is coming in web client only. is it standard warning or else.

  • Suggested answer
    Olister Rumao Profile Picture
    Olister Rumao 4,009 on at

    Hi Ramesh,

    Are you using any API?

    The ETag error generally occurs when you are using any API or Page as a WebService as ETag is used to identify a record in NAV/BC.

    You can raise a Microsoft Support Ticket if it is an error in Standard Installation!

  • Ramesh G Profile Picture
    Ramesh G 97 on at

    Hi Olister,

    No API.

    Not published as Webservice.

  • Community Member Profile Picture
    Community Member on at

    Hi Ramesh,

    Are you still getting this issue? If you are, then I think a rollup of BC will fix the issue for you. I've noticed this on two customers, one on BC 13.0 CU7 CU6 and on BC 14.0 CU1 RTM and rolling up to the latest version fixed the issue

    *as long as the web client itself was reinstalled. Simply rolling up the files and restarting didn't fix it.

    It seems that only BC 14.0 CU1 and above is fixed, but for BC 13.0 CU6 to CU11 has this issue despite MS claim it was fixed. 

    https://github.com/microsoft/AL/issues/4916

    Hope this helps.

  • Ramesh G Profile Picture
    Ramesh G 97 on at

    Hi Redon,

    The same error coming even in the D365 BC 14 CU6 web client.

  • Community Member Profile Picture
    Community Member on at

    Hello, I have exactly the same problem with version 14.0.29530.0, did you find a solution ?

  • Community Member Profile Picture
    Community Member on at

    Hi!

    I had the same problem, also with version 14.0.29530.0. The problem disappear when I set any filter on the list page or when I don't show the field xxxx.field on the list page. Maybe this is a workaround for you too!

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

November Spotlight Star - Khushbu Rajvi

Congratulations to a top community star!

Forum Structure Changes Coming on 11/8!

In our never-ending quest to help the Dynamics 365 Community members get answers faster …

Dynamics 365 Community Platform update – Oct 28

Welcome to the next edition of the Community Platform Update. This is a status …

Leaderboard > Business Central

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans