Forum Discussion
RyanPflederer3
5 years agoQuickbase Staff
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
------------------------------
- BlakeHarrison5 years agoQrew CaptainI've just downloaded the app and started testing it out with a smaller app. When the script hits Get Reports for one of the tables, though, I'm getting a permissions error and the script crashes.
------------------------------
Blake Harrison
bharrison@datablender.io
DataBlender - Quick Base Solution Provider
Atlanta GA
404.800.1702 / http://datablender.io/
------------------------------ - DanPark5 years agoQrew MemberHi Ryan, this app is great! It definitely helps with many aspects of configuring QB apps!
I have a question about configuring apps that I add to the Library that are from different realms. I was able to set up the Pipelines to update changes in the to the apps, but making changes fires off all the Pipelines. the Correct Pipeline makes the changes, but the other Pipelines that are not related to the app I'm updating fire and return access errors. In your instructional video you mentioned that additional lines of logic need to be added to the YAML code. Could you help me out with this? I would like only the relevant Pipeline to trigger but due to the YAML code, I am not able to edit/update the Pipeline...
------------------------------
Daniel Park
------------------------------- RyanPflederer35 years agoQuickbase StaffHi Daniel!
Within your existing Pipelines, you can update these to be realm specific by simply adding thisAND{38.EX.'realmName'}
to the Advanced Query in Step A. Just swap out realmName with the name of a specific realm. Once this is completed the Pipeline will only trigger on changes to that particular realm. Just make sure that you've got the right usertoken coupled with the realm.
Hope this helps!
------------------------------
Ryan Pflederer
Implementation Consultant
Quickbase
------------------------------
- EmberKrumwied4 years agoQrew CaptainJust 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
------------------------------