Form Alias in NSF Components (Composite Application)

Hi all,I’v found an issue regarding the naming of the Form (alias) that you want to use in a CA.

STEPS TO RECREATE THE ISSUE

  1. Create on a domino 8.5 server a blank application

  2. Create a form (test1) with F001 as alias (you can use FXXX where XXX is any number). Inside the form put a field, only to avoid to have an empty form

  3. Create a form (test2) with FTEST as alias (you can use FYYY where YYY us any text). Inside the form put a field, only to avoid to have an empty form

  4. Create a blank composite application.

  5. In the composite application editor create 2 NSF components based on the forms test1|F001 and test2|FTEST

  6. Put the test2 component in the default page of the CA, it will work. Put the test1 component and you’ll have an error (unable to create document, database does not contain design element)

Now try this:

  1. Change ONLY the alias F001 in V001 in the application with the 2 forms

  2. Modify in the CAE the NSF component that was built on F001 so that it uses V001

  3. Put the modified component in the default page of the CA and it’ll works fine.

So, it seems that something goes wrong when the alias is composed with the letter F followed with numbers.

I tried only with F and V but, maybe, something could happen with other letters.

Because of in the documentation there aren’t limitation with the naming of design elements if think that this could be a problem.

In my case, I’m trying to do a CA starting from an application with 13 databases where ALL the forms have an alias formatted with F followed with numbers (views have V with numbers, pages P with numbers and so on) so you could easyly image that this is a very serious problem because I have only two options: 1) rewrite the application with different aliases (not applicable) or 2) don’t implement the CA (a pity because some customer may be interested).

I’d like to thank you for your time and attention.

Alessandro Bignami