Al: FieldGroups - All tables need default DropDown FieldGroup

[GreatScott000]

It is not possible to extend a FieldGroupwithout it already existing. E.g. the Item Variant (5401) table has no DropDown FieldGroup so I can't add any field from a tableextension to the default dropdown in a lookup. It defaults to just Description.

[JesperSchulz]

This is better to be implemented on compiler level than on application tables. Transferring to al repo.

[atoader]

Hi @GreatScott000 ! This is not currently possible. We will consider it for our backlog.

[tinfister]

Any info regarding this issue? Is it planned to be changed? Any ETA or maybe a workaround?

[JeremyVyska]

This is still an issue.

Either add default DropDown and Brick fieldgroups to all base tables or change the TableExtension object to allow us to create it.

Either will suffice, but right now, it's just a hard stop. We also can't change LookupPageID, so we're very stuck here.

[Update-ABS]

I can understand why you may not be able to add fieldgroups with mixed base/extension fields, but I do not understand the underlying reasons why we can't specify fieldgroups with all base fields, or all extension fields. Likewise with the lookuppageID. This is a very difficult restriction to work with.

[radovandokic]

Any ETA or maybe a workaround?

[atoader]

Thank you the input! We have had a lot of great suggestions from the community and we have tried our best to prioritize the most important ones for the Fall release. Unfortunately, this did not fit in. It would be of great help if you could post this to our Ideas forum at https://aka.ms/BusinessCentralideas, or vote up the idea if its already there. It will allow us to better prioritize the issue for a future release.

[AbsolutelyFreeWeb]

@atoader @JesperSchulz this is something that was possible before, and is now lacking functionality. Without giving us a work around, why do you not treat it as a bug rather than a would be enhancement ?

[JeremyVyska]

@JesperSchulz @atoader - Hey, when the Fall release comes out as pure AL code, could the community do one massive pull request with default DropDown and Brick fieldgroups to all the objects that are missing them? From what I understand, the base app will be in GH, so we should be able to get this done where you cannot, yes? (That's not criticism - we just need this fixed.)

[JesperSchulz]

I'm afraid we will not be publishing the BaseApp on GitHub - at least not now. What we _are_ publishing, are the modules and add-on extensions we extract out of the BaseApp one by one. The reason for not publishing the BaseApp is that we would be struggling to keep up with the inflow of pull requests, as we know that many partners have many great ideas - but not all of them are compatible with each other and desiderable in the standard product. It would require a big investment to understand and polish all of the incoming suggestions. We're not in a state yet, where we can make that change and go truly open source on all of our application code.
So, for now you will have to stick with http://aka.ms/bcideas - try to get enough votes and we will take a look at it. And maybe some day, everything will be aligned to make the big move to open source all of our code - but that does require build system integration, a community which is prepared to chip in and review, a more structured base code and so on...

[JesperSchulz]

With that being said, it does not mean that we won't be looking at the concrete issue mentioned in this thread. My previous comment was purely on the aspect of open sourcing the BaseApp.

[markusfjolnisson]

@JesperSchulz @atoader Are there any plans to implement default fieldgroups for atleast the main header tables (Sales Header, Purchase Header etc...) to allow us to work around this issue while you find a propper solution?

[JesperSchulz]

Hi @markusfjolnisson, if you could give me a complete list of the tables you'd like us to implement default fieldgroups in, I will process it for the upcoming major and minor release - while we wait for the correct solution in our platform.

[JesperSchulz]

Ideally, I would also need the definitions of the fieldgroups. That would speed up processing ;-)

[markusfjolnisson]

Hi @JesperSchulz, Thanks for the fast response. It is a pleasure to be able to interact with your team on these issues!

As i see it, the most important tables would be the unposted header tables, and their corresponding line tables...

36 Sales Header
37 Sales Line
38 Purchase Header
39 Purchase Line
295 Reminder Header
296 Reminder Line
5740 Transfer Header
5741 Transfer Line
5900 Service Header
5901 Service Item Line
5902 Service Line

As for the definitions of the fieldgroups, i think the current default "Drilldown" options are fine. If I remember correctly, when a fieldgroup is not defined, the system uses the primary key of the table and the description or name field (If that is a field included in the table). My problem is not the default fieldgroups used by the system, but that i am unable to add a field to the dropdown list to aid the customer in registering data.

[JesperSchulz]

:-) I get that! I just don't want to add default fieldgroups (which are used by the majority of our users), which make the product worse. But I'll check what the functionality defaults to, and then I will set those explicitly on the tables you mention.

[TKapitan]

Hi @JesperSchulz
We have just implemented BC15.0 (upgraded to 15.2) and default fieldgroups are really missing and we are struggling with that a lot... The project is about 300MD and it is very hard to explain to our clients that we are able to change almost everything except this (that is from their point of view so easy).

I know that we can change baseapp (we are onPremise); however, we did the whole project without any change in baseapp...

Could you please add the default DrillDown fieldgroup to:

• Shipment Method (ID10)
• Transport Method (259)
• Payment Method (289)
• Shipping Agent (291)
• Bank Account Statement (275)

[JesperSchulz]

I surely can! Adding those 5 tables to my pack to be released with next minor :-)
Any other requests out there while I'm at it?

[tinfister]

table 99 "Item Vendor"
table 7012 "Purchase Price"

thanks

[JesperSchulz]

You got it! Final call for more tables ;-)

[JesperSchulz]

Pack is being processed in the build system now. All requested tables will be released with the next minor update. Keeping this issue open, as the proper implementation through language support is pending.

[miracleitconsulting]

I surely can! Adding those 5 tables to my pack to be released with next minor :-)
Any other requests out there while I'm at it?

Sorry if i'm too late.. but can we have dropdown fieldgroup for Bin Contents table as well?

[JesperSchulz]

I'll see what I can do for you :) The other fieldgroups are getting released with the next minor end of month.

[miljance]

So, no hope to be able to define the fieldgroup for a base table from extension?

[ALDeveloperin]

So, no hope to be able to define the fieldgroup for a base table from extension?

H,I I agree this should be available to create new FieldGroups in AL extensions. When can we expect it?

[JesperSchulz]

@pborring/@atoader, that question would be for you to answer.