@Levent_KULACOGLU Can you say more? I donโt quite understand. Weโre working on allowing you to pull in data from your cloud data provider, if thatโs what you mean.
@tony Iโm talking about appending JSON descriptive headers to the spreadsheet columns and changing its type qualifier without a need to regenerate the column structure. For example: I might have a client who desires to add his own forms to the app as per his needs in the future, and I can just give him a provisional table where he can choose the type of the columns/fields he want to use and then I can append those as JSON header to the sheet and when he syncs the app, voila! the form is ready to use
For example, a JSON header like this: AppSheet:{โDescriptionโ:โExpected due date:โ,โIsRequiredโ:false,โTypeโ:โDateโ}
@Bellave_Jayaram what you have mentioned is another approach for sure. I also think that it might be very much beneficial provided we can have the flexibiliy of export/import app structure as JSON for example. I can count many use cases here.
@Levent_KULACOGLU I am not sure what segment of the AppSheet user base SPEC is intended for. I believe that users of different skill levels will need slightly different things. I donโt think most users would care to export an app definition. However, I think advanced users will find it useful to manage many tables, views, slices, actions, workflows etc. and also to build (and test and maintain) app structures in a more modular way via a declarative syntax not too different from the SPEC syntax.
In the same way that the Google forms to AppSheet app interface inserts comments in headers. I believe Levent is asking if we did that either manually or programmatically, could SPEC consume that and auto-update the app without us having to regenerate.
I would actually like it if I could write assertions/statements to a text file and an already existing app could read it and incorporate it into the app.
I am thinking of assertions such as the following:
Table:โTBLโ hasColumns 10
TBLCol1 = {โNameโ:โAโ, โTypeโ:โTextโ,โฆ} TBLCol2 = {โNameโ:โBโ, โTypeโ:โNumberโ,โฆ} โฆ Table:โTBLโ hasSlice โTBLSLC1โ Slice โTBLCSLC1โ includesCols {โAโ,โBโ,โEโ} Slice โTBLCSLC1โ hasViews {โListโ:โClientViewโ,โDetailโ:โCV_Detailโ,โFormโ:โClientFormโ}
User | Count |
---|---|
44 | |
28 | |
28 | |
21 | |
13 |