JeffHughes
Qrew Trainee
Joined 4 years ago
User Profile
User Widgets
Contributions
Re: Getting the DBID from an Alias
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.Re: Getting the DBID from an Alias
Correct. But I want to build a field in Document Templates called "Table Alias" and then formula called "DBID lookup" so I can put [_DBID_CUSTOMERS] into the Table Alias in Document Templates and then a lookup field that tells me what dbid that alias is representing. So I can then quickly grid edit all of my document templates.Getting the DBID from an Alias
I want to be able to put a text field into a cell and it be the table alias, then another formula field that converts it to the DBID. Reason being when we copy an app, the tables stay the same, but the DBIDs all update and we have to go manually change all the juiced URLs.Re: Limit Relationship Choices based on another field..
I did this, but I wanted to further limit the selection. So I ended up going with a new form and showing that form on Grid Edit. It worked. But then, when the user hits edit on the parent. It didn't work.... So I went back to the a conditional filter and created a formula in both to basically result in a combo of project number and "_1" if I wanted it shown, and then matched that in the other table. And it works like a charm now.Re: Reference Current Parent with Button on Child
I follow that, and I thought about that as an answer. My fear is User 1 selects "Set Focus" and it records the record ID to a table which I can then lookup in my PO to trigger the "Link to Record" button. But User 1 is halfway through their list and then User 2 clicks "Set Focus" on a different report, and now User 1 is clicking the link button and thinking its linking to the report he's on, but it's actually linking to the report User 2 is on.
