|Jenzabar-provided data sources vary according to your school's licenses to CRM Candidate and EXi Events Management.
|Any data sources or string replacers you set up are available to all forms within the FormFlow instance.
Data sources are SQL statements that can be used to populate information in different ways across multiple forms. Data sources can save the form user time completing information you already have in your database, help ensure inaccurate information isn't entered, and can keep questions limited to specific choices. There are five types of data sources you can use:
· Options can use information in your database to populate drop-down, radio button, and checkbox lists. For example, you can populate a state drop-down list on your form with a state list from your EX database.
· Auto Completes provide a typeahead feature that lets form users start typing a field/question response and then pick from a list of options that automatically appear.
· Look Ups use a 'trigger' question which completes other fields on the form based on information the form user enters or selects. For example, if a faculty member enters their email address, the first and last name fields on the form can be automatically completed for them based on information you have in your database.
· Access Control Lists let you limit who can access your form. For example, you may create a homecoming voting form, but only allow upperclassman to vote.
· Waiver Codes can be used when a payment is associated with your form and your school allows the fee to be waived in certain circumstances.
You can use Jenzabar-provided JZB SQL statements or create your own so you can populate your forms with frequently used database information. Data sources are not limited to one form. You can reuse them as needed.
Jenzabar-provided datasources are read-only and cannot be customized. These datasources are prefixed with JZB. For example, "JZB - Event Look Up by ID".
Prefix a value with ## in the SQL to hold the place for a value to be inserted at execution.
Database columns frequently use CHAR data types, which pad values with trailing spaces. This can cause issues when comparing the user entry with what exists in the database. Extra spaces might prevent it from matching.
For example, database might have "NC" as a state and when the user enters "NC ," trailing spaces might be added.
Use RTRIM() on char and nchar columns to ensure values match.
Set Up an Auto Complete
Set Up an Access Control List
Set Up Waiver Codes
Why won't my datasource populate my drop-down question?
Multi-select Question Options