FSM Alias tables for FSM tables

Hi @AnupamaHN ,

Alias table is merely a reference to the primary table where it does not contain the physical table structure. Why aren’t you using the PERSON table instead?

Hi @SAMLK 

PERSON table is already used in the header part of this screen. But in this scenario I need another connection between person and team member table. Please fins the UI joins below. 

So there’s no possibility to update the record through the alias?

Kind regads,

Anupama

Hi @AnupamaHN,

   You can use Person table again to join it with TEam_member table.

Directly set Person table with person_id and team_member with person_id

Thanks

Sumit Joshi

AnupamaHN wrote:

Hi @SAMLK 

PERSON table is already used in the header part of this screen. But in this scenario I need another connection between person and team member table. Please fins the UI joins below. 

So there’s no possibility to update the record through the alias?

Kind regads,

Anupama

Hi @AnupamaHN 

Not required to join the team member table with the person alias table. Try to join person and team_member tables together with person_id primary column. Then get the relevant column from the person metadata as the PERSON is the one with the physical table structure.

Hi @SAMLK 

Thanks for the help. Joining the team_member with the person table directly won’t be possible as there is another conncetion between the same tables with the person_id_leader column. So I have to use an alias for the second connection. 

Apparently it is possible to edit a field coimg from a FSM alias table. Please see the below community post.

But in my case it wasn’t possbile. Wondering whether there are some other setting that needs to be in place?

Kind regards,

Anupama Nagahawatta

Can you share all the relationships with the primary keys which you have mentioned here?

Hi @SAMLK 

Sure, please refer the screenshots below

Thanks, can you also explain the header section and the crew listview as well? I will try to replicate the same in my local environment

Thanks heaps, 

Header section: It is the baseline my profile screen structure for the technicial portal which is the person record

My crew tab: Idea of this tab is to have a members under a certain person record. The header person record will be the team lead specified for a specific team in the team record. My crew tab in a duplicate view of the team member tab on the team screen

Hope this is clear

Hi @AnupamaHN,

    Just create a person2 in custom Metadata and there is field called “Alias of Table Name” there put “Person” as table name. Then try to create a relationship in Child editor relationship.

Though I am not sure it will work or not but in system it will create a table person2 and then you can establish relationship here.

Thanks

Sumit Joshi

Hi @AnupamaHN 

Sorry for the delay in response. I have just replicated the scenario in the ui designer with a custom screen. This anyways seems to work for me even with the baseline PERSON2 alias table. The records were updated successfully. Yes your argument point was correct the datatable structure points towards the physical table.

Please check the item path for mobile phone as well. You might need to set that manually if it’s not pointed correctly

Hi @SAMLK 

That’s very strange, I have the Item path set as well but it doesn’t allow me to add a value to the mobile field and save.

Can you update the record?

Yes I can update the record,

What’s the FSM version that you’re using?

Can you also check the relationships as showed in the ss below?

@SAMLK

I’m trying this on the web client could there be a difference?

When I try to change and save nothing happens. Then when I try to refresh the page it asks whether I need to save. Then when I click YES it rolls back the change I did and save it

Relationships on the UI are indetical to yours and I’m using FSM6U26

@SAMLK Thank you so much for the help