Al: LookupPageID and DrillDownPageID

Created on 19 Jul 2017  路  14Comments  路  Source: microsoft/AL

We cannot change LookupPageID and DrillDownPageID properties of table to create extension,
we have created different pages than standard pages to use while selecting the values etc. and due to above limitation we are not able to achieve it.
Can you please review to provide access to change above properties.

bug ships-in-future-update suggestion

Most helpful comment

Hi @pmohanakrishna, @lvanvugt,
I think we have reached a consensus that these properties should be customizable in extensions.

All 14 comments

Thanks, we will look into this.

any update on this?

Apologies for the delay, slipped away. Checking...

This requires some platform support, but generally it can follow the "last man wins" strategy in case more than one extension modifies the property.

After further discussion between different teams it has been decided that LookupPageID and DrillDownPageID properties should not be customized in table extensions. The reason is that if multiple extensions change the same property, then the "last man wins" strategy will be confusing as it affects the behavior of the system, and not only the display (such as caption/description properties which are customizable).
Apologies for setting wrong expectations before.

@dennisfrostlander I understand the reasoning, but how am I going to get the following working:

  • I am creating a dependent extension (B), depending on one of my own extension (A)
  • In B I extend a table in A (TableA) with a new FlowField (in a table extension object, TableExtB)
  • CalcFormula is pointing to a TableA
  • I am adding the FlowField (through a pageextension object PageExtB) to a page in A (PageA)

OK, no issue so far, but now I would like to enable that the user can drilldown on the FlowField. So, I need to have a page linked to TableA, by means of the DrillDownPageID property, but this is not enable in AL.

How to get this working?

Hi @pmohanakrishna, @lvanvugt,
I think we have reached a consensus that these properties should be customizable in extensions.

Great. As we are mainly on NAV 2018, can I apply for a downgrade?

Sure, but only when this issue gets resolved here on the latest version of the product.

I recon a milestone will be attached to this issue in due time?

And BTW, what about this issue related to it: https://github.com/Microsoft/AL/issues/2917?

Sorry, was not involved into the related issue. We'll provide feedback on it shortly as well.

@dennisfrostlander what is the fix here and how to use that? any help is appreciated.

Hi @dennisfrostlander ,
please look at my issue 4363 where I propose a separation in the definition of the tables in the physical part and the non-physical part, together with some other things to cover the OnPremise software maintenance scenarios of final customers like us.

@StanislawStempin

Was this page helpful?
0 / 5 - 0 ratings