Design an external resources database / DXL importer / API C

HCL Domino Domino Forum
1

Hello,

What I am trying to do is to design a notes database template that will contain forms / script libraries / framesets /

pages… that are common in most databases in order to inherit each new relase of a function/page/subform in all my DBs in

one shot.

I currently use a system of external resources for CSS, JS but these are documents, not notes elements.

One great thing would be to be ability to log which elements are exported/imported (in which DB…), that is why using DXL

classes seemed to be really interesting.

I have tried two ways to build an external resource DB :

1 - use a main template that will be the parent of other templates and which will contains only common elements. It seems to

be a good way to do it but it supposes that every note elements in the database is defined as “Do not inherit from template”

(or anything like that - I do not have the english version). If not doing so, the chidren template would be erased before

inherit. This could be ok for me whether there would a mean to activate this option automatically (I am a dreamer, I know…).

2 - Use DXL importer / DXLExporter class in Lotus Script

It would have been a perfect solution if there would not generate strange results

(see the post of my colleague at

http://www-10.lotus.com/ldd/nd6forum.nsf/DateAllThreadedweb/856d861e6fa695fd85256e2b0032c40d?OpenDocument)

Pb : import fail from 2nd import of the same elements

(subforms, shared fields, framesets, image resources seem to operate smoothly but not pages, script libraries, and sometimes

forms)

Does anybody have ever built such system ?

Any idea of a way another way to do it ?

Thank you all for helping me,

Sylvain

2

Subject: design an external resources database / DXL importer / API C

  1. This property “Proihibit design refresh or replace to modify” is a P in the $Flags item. You can easily write code to set it.2. It looks like DXL import is broken when replacing some design notes. But it works OK when creating design notes. So a solution might be to delete the old design notes before importing the DXL.

Christine Berault has pointed out that the SelectionFormula in NotesNoteCollection is also broken. This makes it harder, but you can write your own selection code using GetDocumentByID to get each NotesDocument, and you can use Remove to remove it from the database.

3

Subject: RE: design an external resources database / DXL importer / API C

Thank you so much Rod,

I finally use the second option (not use REPLACE_ELSE CREATE but CREATE after having deleted) :

1 - export all documents from the template DB

2 - remove those docs (prefixed design item) in target DB

3 - import all design item into target database

it is working well

Thank you,

Sylvain