Hey Mick Jackson what did you have in mind for this? how would you want to use the data? 🤔
Are you thinking of being able to use them in Front-End Submission Forms for WebApps?
Mick Jackson
•
Nov 27, 2019
Martin Sanderson: correct. Front end form webapp submissions which will display in front end webapp lists. It will also allow us to have the crm and we apps separate for the build, but bring together for certain components where crm users are tied into components of the webapp. I have 2 projects that could benefit from this at the moment so I can walk you thru it if need be.
Mick Jackson
•
Nov 28, 2019
Martin Sanderson: I also think that once we can assign a crm user to a list, we may be able to use the list within webapps as well.
Example: I can create 2 separate forms for team 1 and team 2 respectively. The forms may have different custom field sets. The crm data against team 1 including the field sets, can be used in webapp A. Where webapp A has loads more data fields assigned to allow potential slice and dice of data. The crm data against team 2 including field sets, can be used in webapp B, along with a data field linking to webapp A, which may be a field from the crm data base from team 1.
Short of rebuilding a crm as a webapp, it would make more sense to allow crm database to be a data source.
(also note: it would be good to be able to assign a selected field to the data source)
Log in to comment and vote
Comments3
Martin Sanderson
Nov 26, 2019
Hey Mick Jackson what did you have in mind for this? how would you want to use the data? 🤔
Are you thinking of being able to use them in Front-End Submission Forms for WebApps?
Mick Jackson
Nov 27, 2019
Martin Sanderson: correct.
Front end form webapp submissions which will display in front end webapp lists.
It will also allow us to have the crm and we apps separate for the build, but bring together for certain components where crm users are tied into components of the webapp.
I have 2 projects that could benefit from this at the moment so I can walk you thru it if need be.
Mick Jackson
Nov 28, 2019
Martin Sanderson: I also think that once we can assign a crm user to a list, we may be able to use the list within webapps as well.
Example:
I can create 2 separate forms for team 1 and team 2 respectively.
The forms may have different custom field sets.
The crm data against team 1 including the field sets, can be used in webapp A. Where webapp A has loads more data fields assigned to allow potential slice and dice of data.
The crm data against team 2 including field sets, can be used in webapp B, along with a data field linking to webapp A, which may be a field from the crm data base from team 1.
Short of rebuilding a crm as a webapp, it would make more sense to allow crm database to be a data source.
(also note: it would be good to be able to assign a selected field to the data source)