About table registration
Registering database tables gives the system access to the database tables during processing.
Database tables must be registered in order to reference a table from an external database in an app. You must register a database table before creating an app that uses it. Additionally, you must re-register a database table if modifications are made to the table.
If your Mobile Enterprise Platform system interfaces with multiple enterprise environments, you must register the database tables separately for each environment to ensure data integrity. The apps that are created are assigned to a specific environment, and references made to tables within each app must correspond only to those tables registered to that environment.
When developing apps, ensure all database tables used in the associated app are registered. Additionally, if you copy an app for use in another environment, you must change the app's environment assignment, update the registered tables, and register the function calls within the app for the corresponding environment.
The maximum number of rows to display in the Data Viewer must be set in the General tab of System settings. This must be 10000 or less. Refer to Define System Settings. The data may be filtered by primary keys to narrow down your search.
Download requests and marking records
When creating a database table to be used in a download request that requires records to be marked to indicate use at the device, fields must also be assigned to hold the record status, device name, and call ID (applicable to SQL Server databases) specific to the environment. The system uses the following fields as the default fields: Status, Device, and Call ID. Any field can be used as long as the information it will contain is specified as status, device name, or call ID.
The database table can be accessed through a download request, an output, or a SQL statement. For example, an app can be created for a paperless pick that instructs the picker on the items, how many items to pick, and where to pull the items from. The app carries out the instructions through a download request. The download request contains the database table name and selection parameters for selecting the appropriate records and downloading them to the device. If there are multiple environments, the apps created must be assigned to a specific enterprise environment, and all references made within an app to database tables must correspond only to those tables registered to the assigned environment.
Roles for table registration
Beginning in Mobile Enterprise Platform 9.0 Service Pack 3, only users with the RegisteredTableDataViewer system role can access table registration. Refer to Assign Roles to Users. Custom roles must also be set up to allow access to specific tables for a user, and to allow the user to view each registered table by environment, edit table data, or delete table data. Refer to Custom Roles.
Loading...
There was a problem loading this topic