Complex Data Scenario

rfernandez

Hi,

I have the following data scenario:
A main entity with around 60 different fields/attributes.
This attributes were divided into sub-groups of information.
In the end all of them must be related to the main entity,.
For a matter of clarity and design, instead of having one table with 60 columns, they have been divided into several different tables that have groups of information of certain kind, always related to the main entity.
For example suppose the main entity is a car; the car has 60 features, some from the engine, some from the cabin, some for security, and so on.
To make it a little worse, some of the security features are mutually exclusive depending on the cabin type (if the cabin is of type A, then the security attributes will be the ones related to type A cabin, and so for B and C cabin types). That means that there are 3 security tables, one with the specific features of each cabin.
All of these tables are related by a one to one relationship. If I query the main entity I should be able to retrieve the information of all the related tables, via their relationships through the main entity id.

My intention was to have a single form divided into tabs, each tab with a given sub-set of the information, basically the information of one of the "sub-tables".

The problem I find and over which I will greatly appreciate any advice is the following:
In order to relate the information of each sub-table to the main entity/taable, I need the unique id of the record, for which I must have that record already saved in the database so the id is generated.

So, first question, is that possible, using Form states, or some other Form property, before changing to the sub-tabs?
If this is impossible at this time, or simply a bad approach, what would you recommend in order to achieve such a thing?
I think that alternatively a cascading of lists, forms, lists .... could be another possibility, however at first sight it seems much more confusing and cumbersome for data input, than having the tab layout.

Well, this is the scenario. I hope I was able to explain it clearly enough. Otherwise please do no hesitate in asking for clarification. If you find any catastrophic design flaw please feel free to express it. I'm open to ideas. (although a bit constrained by the data model that was kind of given to me)

Thank you very much!!!
Warm regards

gabriel

rfernandez So, first question, is that possible, using Form states, or some other Form property, before changing to the sub-tabs?

Because you have 1:1 relationships between the main relation car and all 'extending' relations (car_type_a, car_type_b), you can simply join all relations on the same form. This way you can fill out fields for all relations at the same time.

When doing this, you can use form states to show/hide fields or tabs based on what type of car it is. For this you would generally have a type attribute on your car relation so that your form states have a criteria to work with as condition (if car is type a show tab T5, if type b show tab T6, ...). Records from relations joined on the same form are automatically created, if you provide data for them in input fields - this also works if you have a new car.

You can, of course, also separate the relations by using list fields with sub forms. In this case, I would hide the list fields until the main car record has been created - you can do this also with form states (if record is new, hide fields X, Y, Z).

rfernandez what would you recommend in order to achieve such a thing?

Nothing really, your approach is fine. Separating data on multiple relations is reasonable and supported in r3 - that is primarily what 1:1 relationships are for. You just need to learn how to use form states and your approach should work fine.

rfernandez

Hi Gabriel,
Thank you for your answer!

Just to clarify, if I join all the relations to be able to input all the values in the same form, then ,when I save the record, which in fact is the main record, all the data fields from the different tabs/relations will be saved in their corresponding database tables with the same main record ID (provided I have entered all the requiered fields for each relation). Is that correct?

Thank you again!

gabriel

rfernandez Just to clarify, if I join all the relations to be able to input all the values in the same form, then ,when I save the record, which in fact is the main record, all the data fields from the different tabs/relations will be saved in their corresponding database tables with the same main record ID (provided I have entered all the requiered fields for each relation). Is that correct?

Why not just test it? It takes maybe 2 minutes to create a new form, join a relation or two, add a couple of fields and save a new record. You don´t need to add all 60 fields to prove the concept, just maybe 2 or 3. Less time than it takes to ask and have someone read and respond to your question, I think :)

But yes, this is how it is designed and works in our apps as well.

rfernandez

gabriel
When you are right you are 🙂.
I´ll do so and let you know!!

rfernandez

It worked like you said.
Thank you!