I have searched the forums but could not find the answer…
We are working to put up a Corporate Phonebook for our global client. (They have a dircat.nsf which is separate from the phonebook). The existing phonebook is a customised db based on the client’s domino directory. It pulls the information from the 4 domain NAB’s that they currently have, once a day.
We now have to extend it to include another db which will contain details of non-notes users (users without a lotus notes ID). This db has to be customised for GUI interface and fields. we created a new blank db - test entries were pulled into the Corporate Phonebook. However, no design changes in the sample db are pulled into the Corporate Phonebook. The server simply states “… 48 Notes purged due to non-native notes format” (not the exact words). And does not pull records created via the customised form. (The customised form creates a Person document in the backend and pushes the field values into it - but, no success!)
Please help !!! how do we handle this, if posible? or is this kind of customisation not possible??
Corporate Phonebook … pulls the information from the 4 domain NAB’s that they currently have…
And you say this Corporate Phonebook is not a dircat. So, what is the code that copies information into it from the NABs? Not the same server task that populates the dircats, so it must be something not supplied by IBM?
… no design changes in the sample db are pulled into the Corporate Phonebook.
This statement implies you expected design elements to be copied, but I assume you’re really just saying that the documents you edited with a modified form aren’t copied over.
The server simply states “… 48 Notes purged due to non-native notes format” (not the exact words). And does not pull records created via the customised form.
When you go online to try and find the answer, the exact words are important, so that you can do a search for them. You’d be surprised how many times “goggling” the error message oulls up an explanation. Of course, if this really is some custom code, you’re not likely to find a match.
The customised form creates a Person document in the backend and pushes the field values into it - but, no success!
The server code that’s doing the copying (or refusing to) apparently has a different idea of what constitutes a Person document than you do. There’s probably some field it’s looking for, which your back-end process fails to create. There’s no way we can tell which fields you’re missing from the information you’ve provided.
You seem to have created something overly complicated. Why have a back-end process to create the document instead of just naming your form Person?
In any case, create the same document using your process and manually in a real address book, and then compare them field by field to see what the differences are.