Picker View Configuration

This site is best viewed in a modern browser with JavaScript enabled.

rafaelrodrigomartinati

Hello guys,

I've a doubt :

I'd like to make an app autoconfiguration option, based on user preferences.
In Backend, I created a table, with all informations I need. So, I used the CRUD function to generate the basic APIs for this table. Its all working fine.

In the console app, I created a picker view and set the keys to access the table. In the PickerDone action, I was able to save the chosen id. its working fine.
But I can't save the other data received by the API. The data saved refers to the first record in the table, not the record that was chosen by the user in Picker View.

My question:

Do I need to create a call to another API, passing the chosen id in Picker View, and then save the data received from this other API?
Or is there a configuration option that allows me to save the data for the id chosen in pickerview?

Many thanks to all the configurators!

paul12

Hello Rafael,

the API can be created in both the ways looking into the requirement.
-If there are two picker using the same API, where the output of one picker is the input for another picker, same API can be used.

Question: But I can't save the other data received by the API. The data saved refers to the first record in the table, not the record that was chosen by the user in Picker View.
Comment: Do you mean despite of selecting 2, 3 option from Picker only one value is being saved? If multiple option needs to be saved set the Key name to datasource value in the picker: it is the value to be passed from picker on the API.