Hi Readers,
I have two tables
Table-A with columns:- ID_A, Job_Role, Company_NameTable-B with columns:- Member_ID, Name, PhoneNumber, ID_A
which are related as one to many relations
I have created record type for different these tables and added relation ships in the record type as well, Would like to know can we consolidate them as below requirement
rows which i want to display are
Below are the tables structure
Table-A is as below
Table - B is as below
Discussion posts and replies are publicly visible
Yes. That is possible. In a local variable, you the query record type and use the output in the grid. You will be able to access the related fields of the record by accessing its relationships. ie. recordType!Member.relationships.relatedRecord.fields.fieldName
Since the grid you're looking for has one row per member, I'd suggest making the record type for table B your source for the grid. Then, you can reference fields from table a by using relationship references. For example, you can select the job role by referencing the field recordType!A.relationships.B.jobRole.
If you're still having troubles, can you post your code and any errors / issues that are occurring?
Yes vaddhicharanc0001, it is possible. Apart from the above mentioned solutions, you can even create a view in database as per the requirement.
And create a record to retrieve data from that view. Hope this helps !!
We can create a view from multiple tables and how can we use that ??
Create a record Type object for that view as you do for a table and then use it in the grid as required.
Sure this is possible, but in general I wouldn't recommend doing this in most scenarios - using related records is a lot easier to setup and change, and it doesn't require any database experience.
Hello there! I have a similar scenario. I have two tables: Tasks A and Tasks B and I need a Consolidated Task record to show the columns both tables have in common.
One option is to create a DB View with the subset of columns from each table as
(Create view ConsolidatedTasks as Select column1, column2 from TasksA UNION Select column1, column2 from TasksB)
but then I'll have to create an API and integration to retrieve the data for the View as the source for the record type, right? It feels like over complicating it. Any suggestions for this scenario?
If you want to have a synced Record (and be able to create relationships), I'd say that it's the only way to do it.
Otherwise, if you don't need synced Record Types, you could also create a view and just create a non synced Record Type against the view.
Yea you're right. Thanks for your response!