Data planning

why create a data plan? data is used throughout the jigx app, knowing where the data is coming from or going to, how to use that data on the device, whether online or offline, what data you can prefetch and made available on the device, and what data you will fetch just in time is important to design before building apps this saves developers time and ensures the correct data is used from the beginning steps map out the data for the app this includes the data that will be used on each screen are you using pre existing data sets or creating new data sets? decide where the data is coming from or going to, for example, microsoft azure sql docid\ wgljzmkh6kqe3purupgps , rest docid\ jjuid0htf7uk1c8rvntkm , dynamic data docid\ ghdcdrnekxytnuvin5whf (local or global), salesforce or microsoft onedrive docid\ k6zgcjcv5tmavjf8srpc3 map out the tables and joins that will help visualize the data and assist when building the data out create an entity relationship diagram to model the app data draw where the data points are needed on your sketch or miro board created in the solution design step most importantly, decide when to load data in the app and on the screens for example, when must you cache fresh data from sql vs using local data, this helps with offline capabilities see when to load data docid fftw9cmuykuwkqzqpu4l to understand the various options, benefits, and drawbacks considerations design the data flow with offline in mind this helps to know when to plan the loading of data on an app privacy and keeping data safe are important, in this instance, it would be better to use an sql server that provides this functionality data grows with time, plan for scalability data must be structured in the backend clean data ensures you show the latest and applicable data to your users you can add filters and search fields to assist users in the app screens using relevant clean data from the start creates a real user experience while developing having the screens drawn out, as described in the solution design section above, helps visualize what data you need and when to load the data determine when you want to save or send data to a database, for example only once a submit button is pressed this is important as it determines what code is required at build time in jigx if the same data is reused in multiple screens, you can decide whether to create a global data source that can be reused in different jigs include this on the data plan as it helps the creator know where to build the datasource in jigx builder global data is created under the datasources folder and referenced in multiple jigs, and local data is created in the jig file for use in that single jig tip having to create a database can be time consuming or daunting, use tools such as chatgpt to create a database, a database script, or build a csv file for a data structure for dynamic data a csv file can be data docid\ zjbvpf4gxbcdqsesfwlt to jigx management to create the tables and data in jigx use actions https //docs jigx com/actions to move data from screen to screen when using rest or sql, you need functions and stored procedures decide what the functions will do use postman to understand the properties required be smart in the design of data by thinking of creating experiences, for example, data can be shown as charts rather than lists