What would be best possible approach to create a lookup table in AEM site? | Community
Skip to main content
Level 2
September 8, 2021
Solved

What would be best possible approach to create a lookup table in AEM site?

  • September 8, 2021
  • 2 replies
  • 700 views

We are thinking of implementing the lookup table as a content fragment where the content author will put in information as a key-value pair. Now if we want to make use of the content fragment list in a custom component where the values of the content fragment list will be populated as drop-down list, does it seem to the right approach to implement it? Please let me know your thoughts. Thanks in advance.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by joerghoh

Hi,

 

that's an approach, which can work in case your authors need to maintain both key and value fo such a lookup table.

But of course there are limits, for example one Content Fragment per item in the lookup can be a huge overhead. Especially if you need to maintain multiple lookup tables or if you have restrictions on them. Consistency could be a problem if the CFs need to be activated along with the page. And others.

 

it can be a very straight forward model, but it's not a generic solution for such problems.

2 replies

Kishore_Kumar_
Level 9
September 8, 2021

Hi @marjia_yeasmin_tl ,

 

Yes, you can use CF and you need to create a custom servlet to call it under data source for your drop-down.

 

But please check with ACS Common Generic List, as it is straight forward approach to your requirement.

 

https://adobe-consulting-services.github.io/acs-aem-commons/features/generic-lists/index.html 

joerghoh
Adobe Employee
joerghohAdobe EmployeeAccepted solution
Adobe Employee
September 8, 2021

Hi,

 

that's an approach, which can work in case your authors need to maintain both key and value fo such a lookup table.

But of course there are limits, for example one Content Fragment per item in the lookup can be a huge overhead. Especially if you need to maintain multiple lookup tables or if you have restrictions on them. Consistency could be a problem if the CFs need to be activated along with the page. And others.

 

it can be a very straight forward model, but it's not a generic solution for such problems.