I have read a few posts and I just wanted to confirm I understand this correctly.
Objective. When a customer calls us, I want to see if the customer history of tickets. I have an API that given a customerID it will return all the tickets in the table (last 10 tickets).
I then want to show these 10 tickets in an inline list. Each record will return about 5 attributes for the historical ticket. (ticket date, category, rating, custName, company)
Stage 1:
First I need to use a JSON Fetch to call the API with the customerID, this will return the JSON object.
?? Do I need to create the JG parser to break up the values into 5 different columns ?
how do I ensure that if there are multiple users doing lookups they donât override eachothers data ? I assume I can use the USC for the vehiclereg input in stage 1 but how do I do it for the âhelper tableâ
You can either write it directly to your helper table, or use whatever method makes sense to get it in there. Could be a single value, could be a relation + lookup. Whatever.
As long as the source column is User Specific, then every computed column that refers to it will also become user specific. This is the beauty of the helper table approach. You can (in theory) have one million users all working in the same single row table at the same time, and everything works perfectly with each user getting their own unique experience.
This is very interesting and powerful. I think I follow what are you saying. I will give it a shot.
Just for clarification. When you say âhelper tableâ is that a Glide attribute or its just a regular glide sheet that you are referring to as a helper table.
Itâs just a regular Glide Table. Some people call them âworking tablesâ, I like to refer to them as âhelper tablesâ. In general, they contain very little (and sometimes none at all) actual data. Just a bunch of user specific computed columns used for performing a specific task, or series of tasks.
One quick question, when I am creating my working table, is there any way to create dynamic rows, as I am searching history, different searches will result in different number of results. I donât mind creating 20 different placeholders but when I am displaying the inline list, I donât want to be displaying empty records.
Currently I have a text entry component on the main page adding data to a USC row. Each time a character is entered it is making an API call which is causing unnecessary API calls.
If I create a form button, when I hit submit then it is creating a new ROW in my âhelper tableâ but I want it to write to the first row of the USC.
I would create a second USC column that your API will use. When you fill the first USC, then have a âsubmitâ button with a set column action to copy the value in the first USC to the second USC column. That way, the API should only be called when the second USC value is changed.
I was trying something similar, but my issue is that it creates a new row at the bottom and the information is added the that row. I need the information to be added to the USC in the first row, so the working table can be populated
Hi! I think you thould use edit or new screen insted of using form screeen. Also you dont need any edit or new screen just directly use text edit to first us column then press button which had copying to second us column according Jeffâs sudgestion
I feel I am doing something stupid⌠let me share some screen shots
In the back I am using an API to pull in a JSON object and then breaking that up using 2 working tables and then using 2 inline lists to present the data. This first image shows it all working fine, but the issue is that every letter inserted is causing an edit + API call.
I either found a solution or a hack. Instead of using a button to open a form I am using edit screen action and then changing the USC column. It doesnât insert anything until I do not hit DONE.
Not sure if this is the best way, but it seems to be working.
Donât use an edit form, regular form, or any form for that matter. What Iâm suggesting is a button with only a Set Column action. That button wonât open a screen.
It simply uses the Set Column action to move the value from one column to another. Everything can be handled from your same detail screen without leaving that screen.
