I have a relatively simple database I’ve created (I’m not a hard-core Domino coder) in which we are tracking package design projects.
I use the product part number as a parent document, and the package artwork numbers become child documents for each part number (we can have from one to over thirty different packages per part number). All this works fine.
However, I’ve now learned there’s another piece of information I need to track (product MSDS numbers), for which one MSDS number might apply to multiple part numbers (parents) and their associated artwork numbers (children). At this point, I’ve stuck this info in a field in the parent docs.
Where I’m running into problems is in figuring out how to create a view that sorts out by MSDS number. Since I have multiple occurrences of the same MSDS number (across multiple part numbers), I can’t sort these like I can part numbers, which are unique to each product.
After that long winded backstory, my question is whether I can somehow create a “cousin” or third container of some sort in my DB to contain unique MSDS numbers, which can then be assigned from that list to each part number, as well as to each artwork number.
Not looking for code solutions at this point, but if this can be done conceptually, any pointers on what mechanisms to use in Domino (such as possibly using a second child doc, if even possible?) would a huge help.
Thanks,
es
Subject: Can I have two different types of child docs per parent?
not sure if i git your problem right, so my answer might be pointing into the wrong direction…
-
if you want to have a sorting mechanism just for views, and if you already have the msds numbers in all of the part number documents then why not simply use a categorized view showing alls part number docs along with their child docs (are those true responses?), categorized in the first visible column by their msds numbers
-
you can organize your unique msds numbers either
a) in one single doc or
b) - if there’s more info going along with those numbers - in a separate set of “msds” documents.
in both cases you can use simple lookup mechanisms to populate the msds info in the other docs (part number etc.). If the child docs in fact need to have the same info regarding msds numbers and other stuff as their parent part numbers it might be a good idea to incorporate field inheritance upon creation of new child docs.
-Lothar
Subject: RE: Can I have two different types of child docs per parent?
Lothar,
Thanks for the quick reply. It sounds like creating a new form just for MSDSs, and then doing a lookup to select the MSDS within the part number form might do the trick. I wasn’t sure whether I could do something like that or not…
I already have the views categorized as you described, but for reporting purposes, need to be able to sort out by individual MSDS, with “child” artwork numbers underneath those - the way I have it set up currently, I get multiple occurrences of an MSDS number in my view, which requires some analog math to come up with the totals for the report.
Will take a poke at what you suggested and see if I can get it working…
Thanks again,
es