I believe this should be pretty straightforward
I'm just trying to display data from a table that has a link to a table that defines a list of acceptable types.
The first table 'Clients' is:
ClientId
ClientName
ClientAddr
ClientTypeId
and the 2nd table 'ClientTypes' is:
Id
Description
In alpha I build my list using a query
This displays all the fields I want from both tables. Preferably I wouldn't have to show the ct.Id number, but I am showing it now in my list control so that the user can see that synchronization changes have occurred, despite the fact that the user doesn't really know to which Name the ClientId number corresponds.
I have a set of UX controls that alpha generated that let the user update the list and then see sync that with the database.
The way I update the ClientId is by altering the ClientTypeId UX to a drop down that shows ClientType.Name but store the ClientType.Id.
So when the user hits save the ClientTypeId number changes and the ClientType.Name does not change and I would like it to change before the user hits sync so they can see they made the right choice instead of ID number.
I'm wondering what patterns are commonly used in Alpha to store the primary key of a related table based on the selected value and also update sync data.
I'm just trying to display data from a table that has a link to a table that defines a list of acceptable types.
The first table 'Clients' is:
ClientId
ClientName
ClientAddr
ClientTypeId
and the 2nd table 'ClientTypes' is:
Id
Description
In alpha I build my list using a query
Code:
Select c.ClientId, c.ClientName, c.ClientAddr, c.ClientTypeId, ct.Id 'TypeId', ct.Name FROM Clients c JOIN ClientTypes ct ON c.ClientTypeId = ct.Id
I have a set of UX controls that alpha generated that let the user update the list and then see sync that with the database.
The way I update the ClientId is by altering the ClientTypeId UX to a drop down that shows ClientType.Name but store the ClientType.Id.
So when the user hits save the ClientTypeId number changes and the ClientType.Name does not change and I would like it to change before the user hits sync so they can see they made the right choice instead of ID number.
I'm wondering what patterns are commonly used in Alpha to store the primary key of a related table based on the selected value and also update sync data.