I am a beginer user and developer the Lotus note. Someone please help me how to link multiple documents in brother relationships. Please keep in mind that I know nothing about Lotus Notes Desinger. You got to show me step by step. I just start read the book and follow their instructions. I have never been trainned. Thanks.
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Doclink
- Thread starter rvu
- Start date
- Thread starter
- #3
My database have several form documents. In each form documents, one document could link to the other form documents and reverse. I could not link them in parent/child relationship, because multiple documents in one form link to multiple documents in the other form.
For a first application, you could have come up with something more simple.
The only automatic relationship Notes knows is parent/child. One parent may have multiple children.
To do a brother link, and moreover a multiple brother link, you have to code it yourself. In other words, you have to define how to set a document as brother, what criteria to use, and where to give functionality to access the relationship.
Given that you admit being new to Notes, I would suggest that you state your project so we can see if there is a better way to do what it is you want.
Pascal.
The only automatic relationship Notes knows is parent/child. One parent may have multiple children.
To do a brother link, and moreover a multiple brother link, you have to code it yourself. In other words, you have to define how to set a document as brother, what criteria to use, and where to give functionality to access the relationship.
Given that you admit being new to Notes, I would suggest that you state your project so we can see if there is a better way to do what it is you want.
Pascal.
- Thread starter
- #5
Thank you Pascal.
Here is the situation:
For example, there are two forms of documents. In the first SSS document form has a "SSS requirement number" field. Each document has a unique documents number from "S3-1" to "S3-3xx". In the second SRS documents form has a "SRS requirement number" field. Each document has a unique documents number from "RS-1" to "RS-6xx". I want to link "S3-1" to several of "RS-1", "RS-2", "RS-3", etc.. and reverse. Do you know which language code will do the job? and How?
Thank again.
Here is the situation:
For example, there are two forms of documents. In the first SSS document form has a "SSS requirement number" field. Each document has a unique documents number from "S3-1" to "S3-3xx". In the second SRS documents form has a "SRS requirement number" field. Each document has a unique documents number from "RS-1" to "RS-6xx". I want to link "S3-1" to several of "RS-1", "RS-2", "RS-3", etc.. and reverse. Do you know which language code will do the job? and How?
Thank again.
- Thread starter
- #6
I just have an idea to use a view to display "SSS requirments" then next to "S3-xxx" number, I use the some kind of function to display all the "SRS requirement" then the user have a right to select as much as SRS numbers (RS-1, RS-2, RS-3, etc...) as he/she wants then display these number in in column/row and each number has been displayed is a link to the SRS document.
If you have any experience that are similar, please give advice. Thanks.
If you have any experience that are similar, please give advice. Thanks.
It seems to me that what you want is a category.
The SSS number is the common factor beween several documents. These documents also have a specific S3 number.
Therefor, you could content yourself with creating a document with the SSS number in it, and inherit that number in each document that is part of the same group.
In the view, your first column needs to be the SSS number (categorized), then the second column should be the S3 number, then you can fill in with whatever other descriptive fields (non-RichText fields !) you think can help to quickly define the document.
You need to document yourself on inheritance (simple, really) and on how to control creating a new document in the group.
The "link" that you are thinking of is simply the SSS number in each document of the group. Create a new group, and you will have a new SSS number for it.
That should get you going.
Pascal.
The SSS number is the common factor beween several documents. These documents also have a specific S3 number.
Therefor, you could content yourself with creating a document with the SSS number in it, and inherit that number in each document that is part of the same group.
In the view, your first column needs to be the SSS number (categorized), then the second column should be the S3 number, then you can fill in with whatever other descriptive fields (non-RichText fields !) you think can help to quickly define the document.
You need to document yourself on inheritance (simple, really) and on how to control creating a new document in the group.
The "link" that you are thinking of is simply the SSS number in each document of the group. Create a new group, and you will have a new SSS number for it.
That should get you going.
Pascal.
- Thread starter
- #8
- Thread starter
- #10
Who is supposed to do the linking and when ? Are you sure you must have multiple links ? You'll have to have something for the user to be able to choose which link to use.
The other problem is, you are going to have to give the user making the link a resource (button, hotspot, whatever) to choose the doc he wants to link to.
Finally, you are going to have to choose which way you want to make the link. Should it be both ways, should the SRS doc link to multiple SSS docs, or vice-versa.
Depending on the answer, you'll probably have to design the link holders for multiple forms.
Okay, let's say you have linked the documents. Now how do you show them ? I suppose there is not a set number of links for each doc. Some might have 1 link, some might have 10.
In that case, you will need either views to show the linked documents, or buttons to show a list to choose from.
If you use a button, all you need is a minimal interface (@prompt could almost do) and open the linked doc following the user's choice.
If you use views, then you can either embed a view in the form that shows the documents that are linked to the current document (or that the doc links to), or you can use a view that lists one doc type and all other doc types it links to in one go.
This is just a bunch of ideas. Think them over at your leisure.
Pascal.
The other problem is, you are going to have to give the user making the link a resource (button, hotspot, whatever) to choose the doc he wants to link to.
Finally, you are going to have to choose which way you want to make the link. Should it be both ways, should the SRS doc link to multiple SSS docs, or vice-versa.
Depending on the answer, you'll probably have to design the link holders for multiple forms.
Okay, let's say you have linked the documents. Now how do you show them ? I suppose there is not a set number of links for each doc. Some might have 1 link, some might have 10.
In that case, you will need either views to show the linked documents, or buttons to show a list to choose from.
If you use a button, all you need is a minimal interface (@prompt could almost do) and open the linked doc following the user's choice.
If you use views, then you can either embed a view in the form that shows the documents that are linked to the current document (or that the doc links to), or you can use a view that lists one doc type and all other doc types it links to in one go.
This is just a bunch of ideas. Think them over at your leisure.
Pascal.
- Thread starter
- #12
Thank Pascal. I like your ideas. I think the second suggestion "you can use a view that lists one doc type and all other doc types it links to in one go" will work with my database. Could you please show me what command or function should I use to do this? Thanks again. I appreciate your helps.
It is a view, therefor there is no command, you have to build it yourself.
But consider this : if every SRS doc has a field with the a unique key to an SSS doc, then you can list all docs by SSS key. All you have to do is make the first column the SSS key value, then make a second column to sort by form name.
Something like :
That way, the first column groups all docs with the same SSS key (remember to sort !), and second column lists the SSS doc first, then all the rest (if sorted). Of course, these two columns must be hidden.
You might want to add a third sorted, hidden column in order to sort the SRS docs. Use a date value, or some other identifier the user can readily understand.
Now, all this is hidden for the moment, the user still doesn't see anything. It is therefor important to start setting up columns to display actual values - otherwise the view is rather useless.
For example, if every document has a Subject field, then that could be a good value to display. If not, you'll have to decide what information is pertinent in a view to choose the right document. You'll have to do that for both forms, and you'll have to remember that you are designing column formulas for two types of different documents.
By the way, if the fields on your two forms have entirely different names, then your column formulas are much easier (like SSSfield1+SRSfield5).
If you have field names that are identical from one form to the other, your column formulas will probably be a bit more complicated (like @if(Form="SSS";Author;@creation)).
In any case, it will be up to you to design the view that performs exactly the way you want it to. But remember the double-sorting columns in the beginning of your view - that will always work in this kind of case.
Good luck !
Pascal.
But consider this : if every SRS doc has a field with the a unique key to an SSS doc, then you can list all docs by SSS key. All you have to do is make the first column the SSS key value, then make a second column to sort by form name.
Something like :
Code:
@if(form="SSS";1;2)You might want to add a third sorted, hidden column in order to sort the SRS docs. Use a date value, or some other identifier the user can readily understand.
Now, all this is hidden for the moment, the user still doesn't see anything. It is therefor important to start setting up columns to display actual values - otherwise the view is rather useless.
For example, if every document has a Subject field, then that could be a good value to display. If not, you'll have to decide what information is pertinent in a view to choose the right document. You'll have to do that for both forms, and you'll have to remember that you are designing column formulas for two types of different documents.
By the way, if the fields on your two forms have entirely different names, then your column formulas are much easier (like SSSfield1+SRSfield5).
If you have field names that are identical from one form to the other, your column formulas will probably be a bit more complicated (like @if(Form="SSS";Author;@creation)).
In any case, it will be up to you to design the view that performs exactly the way you want it to. But remember the double-sorting columns in the beginning of your view - that will always work in this kind of case.
Good luck !
Pascal.
- Status
Similar threads
