Virtual Empower: App Library
Just wanted to start a thread around the App Library that I presented on during Virtual Empower 2020. My hope is that this can be a place to share other use cases you've come up with, or simply ask q...
Forum Discussion
I've just published an updated version to the exchange. Here's a few of the updates:
------------------------------
Ryan Pflederer
Implementation Consultant
Quick Base
------------------------------
- Capturing App Events
- Capturing Table-to-Table Relationships
- Added a Status to Applications and Tables to quickly identify possible areas for improvement based on Best Practices
- Added a few reports to provide additional insights
------------------------------
Ryan Pflederer
Implementation Consultant
Quick Base
------------------------------
Just downloaded the app and am starting to dig into it. Getting things linked up was super easy (once I referenced the application and not a specific table). One question though; when I go to the Fields table it displays all the fields but it is showing me I have an empty field?
When I look at the list of fields for my tables and compare that to the source app field list it appears as if some fields weren't captured when refreshing the schema. Any reason why the code used to generate an applications documentation would skip or not include certain fields?
Specifically I have a parent-child relationship between 2 tables. The child table contains some additional lookup data fields from its parent. All fields are still in use and working as expected within the source application, however in the App Library one of the child look up fields is returning as empty (all other look up fields returned as expected). When looking at the inventory of these tables within the Library application field 30 of the child and field 14 of the parent aren't listed (child 30 pulls from parent 14). The parent field type is currency and doesn't have any other special conditions applied to it.
Just odd that all other lookup fields were captured/documented, but these two were not.
Thanks
------------------------------
Ember
------------------------------
When I look at the list of fields for my tables and compare that to the source app field list it appears as if some fields weren't captured when refreshing the schema. Any reason why the code used to generate an applications documentation would skip or not include certain fields?
Specifically I have a parent-child relationship between 2 tables. The child table contains some additional lookup data fields from its parent. All fields are still in use and working as expected within the source application, however in the App Library one of the child look up fields is returning as empty (all other look up fields returned as expected). When looking at the inventory of these tables within the Library application field 30 of the child and field 14 of the parent aren't listed (child 30 pulls from parent 14). The parent field type is currency and doesn't have any other special conditions applied to it.
Just odd that all other lookup fields were captured/documented, but these two were not.
Thanks
------------------------------
Ember
------------------------------