[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 164
  • Last Modified:


Any additional ideas to complement sjef's idea in regards to the question above will be much appreciated.

1 Solution
Ok, if it were my database, with certificates.  
The main page is the main document.

Each Certificate is a response document with your certificate # field, who created, date created and the parent unid as a field (which is also $Ref), and the sortdate field: yyyymmddhhmmss.

The lookup view  contains the certificate document only.
                 -first column is the parent unid, sorted, categorized,
                 -second column, hidden, sorted, descending - sortdate.
                 -Third, etc. is whatever you want to display
                 -fourth is parsed column, date + @char(9) + who + @Char(9) + Whatever
On the parent document, you can:
   1. Embed the view, and categorize by parent unid, or
   2. Do a lookup at the top of your form (parent document) in a computed for display field and return the fourth column, and put these results in a computed for display field on the form.

When the user needs to enter a new certificate, they press the button, a dialog box opens (if you need to get information, otherwise, it just creates another certificate and refreshes the parent document so that it shows up in the view.)

I'm not sure what all the comments where in the last question, much too long and counterproductive for my taste...:)

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now