How to get away from a Brick field group in mobile app

(2) Share

Report

Posted on by CU16021850-0

In a Standard Dialog custom page, I've got a "Item No." field which currently has "TableRelation = Item" property.

My task was to change its behavior so the user might be able to search an item also from another custom field. In this respect, I have created a custom "Item Lookup" list type Page where I have added all the neccessary fields.

I have implemented this page on the field's Lookup() trigger (but have tried also on the OnAssistEdit() trigger).
While on the desktop app it is working fine (the custom page is running as expected), on the phone there is a problem. Even though the trigger is Running the custom page, it still shows the fields from the standard Brick Field Group from the Item Table.

Any advice would be appreciated.

Categories:

Dynamics 365 Business Central

I have the same question (0)

All responses (1)

Answers (0)

Suggested answer

OussamaSabbouh 9,995 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!

Hello,

This is expected behavior on the phone client: mobile lookups are rendered in a brick (tile) layout, and the fields shown come from the source table’s Brick field group, not from your custom lookup page layout. So even if your custom page runs correctly, the phone will still display the fields defined in the Item table’s Brick field group. The practical solution is to extend the Item table and modify the fieldgroup(Brick) to include the extra field you want visible/searchable, or use a separate staging/temporary table with its own Brick field group for the lookup. The behavior itself can’t be overridden via triggers.

Regards,
Oussama Sabbouh

Was this reply helpful? Yes No