One approach might be to have the user start by completing a small form where only the IC number is input. (This should probably be stored as a separate table.) A custom Go To View action could be assigned as the form save action, and an if statement in the trigger view field to check whether the IC number exists. If it does exist, use LINKTOFORM to prefill the new full registration with values from the existing record. If it doesn’t exist, navigate the user to a registration form with only the IC number pre-populated.
The behaviour for both cases can happen within one action, and the view will be the same regardless of the condition. Only the number of fields prepopulated will change.
So, within a Go To App View action, your decision as to which fields to prepopulate will be part of the Target formula.
It will basically be something like this:
if( In[IC Number Entered], “Registration table”, “IC Number”),
LinkToForm(“Registration table_form”, “Nana”, Lookup([IC Number Entered], “Registration Table”, “IC Number”, “Nana”),
LinkToForm(“Registration table_form”, “IC Number”, [IC Number Entered])
)
The if statement tests whether the IC number is found in your registration table. If it is found, then any values from that registration can be obtained with Lookup() and added to the value pairs attached to the LinktoView() function. If the registration number is not found then the only value we can prepopulate is the registration number, in the negative case, we include that as a value to prepopulate.
I tried to enter the above formula into the target part of ACTIONS but it cannot be use. It turns out invalid. Should i remove the word IC NUMBER Entered or just leave it? Or problem on other area?
Im sorry i dont know much about the whole formula thing. Thanks
The formula I gave was just a starting point for you. You’ll need to put
in the real field names and may have some other tweaking to do. That’s all
the help I can give you.