We're reclaiming inactive PDIs to keep them available for active builders. Learn what's changing, who's affected, and how to protect your work. Read More

merging 10 custom tables into one table

rBh
Tera Contributor

3 weeks ago

Spoiler
 

Hi Team,

 

Our client has requested that we merge 10 custom tables into a single table and introduce a "Type" field containing the names of all existing tables as dropdown values.

Each of the current tables has:

  • Different approval processes
  • Different UI Actions
  • Different business processes
  • Different user access restrictions
  • Different form sections and fields

In the proposed design, based on the selected Type, the system would display the relevant fields and sections and execute the corresponding approvals and UI Actions.

Could you please advise whether merging these 10 tables into a single table is considered a best practice? Given the differences in processes, security requirements, UI configurations, and business logic, would it be better to retain separate tables (or use a parent-child table structure) instead of consolidating everything into one table?

 

Please share your recommendations and any best practices that should be considered for this design approach.

 

Thanks,
Bhavana

0 Helpfuls
  • 395 Views
6 REPLIES 6

rBh
Tera Contributor
In response to yashkamde

3 weeks ago

Hello Yash,

 

The client has been very clear that they cannot purchase additional licenses, and since each table represents a unique entity, a parent-child relationship approach is not applicable in this case. The primary constraint we are trying to address is the custom table licensing limit.

 

Could you please review the approach I outlined below and let me know if you have any alternative suggestions or concerns? At the moment, consolidating some of the smaller tables into shared tables appears to be the most feasible option given the licensing restrictions.

 

Thanks,
Bhavana

0 Helpfuls

yashkamde
Mega Sage
In response to rBh

3 weeks ago

yes,

I don't see any major concerns with the proposed approach. The main consideration would be ensuring that the consolidated tables remain manageable over time and do not become overly complex as requirements evolve. As long as the entities being combined have sufficient commonality and the governance around record types is well defined, I believe this is a feasible approach.

 

Given the licensing limitations, I agree that this appears to be one of the most practical options available and solution appears to be a practical.