Forum Discussion
For the Document Templates take you can change the fields which hold the table IDs and the App IDs to be formula fields. That will break the Juiced configurator tool as it won't be able to write to them, but for the parent template table, Its really just a list of fields which you cab maintain manually.
But the syntax for the settings field for the Subtables would be horrible to do manually, virtually impossible. I think you would need to ask Juiced for a suggestion.
- JeffHughes3 months agoQrew Trainee
I just need a formula that converts alias to DBID.
We copy apps, and then have to go change the formula of every document template and sub template through grid edit and change out the DBIDs. I have to have two screens and lookup the new DBID. If I had a field in there that could just lookup the dbid based on the alias, the alias doesn't change, so I could essentially grid edit and then just copy paste rapidly into the formula.
I found API_FindDBByName, just not sure how to convert that into a rich text field.
- MarkShnier__You3 months ago
Qrew Legend
OK, now I finally understand the challenge. Took me a while to "get it".
Not saying it's pretty but here is a solution.
For the Document Subtables report make a long formula field like this.
Case([Record ID#],
1, [_DBID_CUSTOMERS],
2, [_DBID_PRODUCTS],
etc.
Then you add that field as a column to the report and use copy paste to fix the table ID which is embedded in that crazy long Juiced string.
Similarly, you do the same idea with the Document Templates table. The App ID will just be the formula AppID(), and if it needs that Document Subtables ID then that also would be like
[_DBID_DOCUMENT_SUBTABLES].
But for the Master table dbid, that would be another long Case statement.