Duplicate design elements in Addressbook

we have two views with the same name ( same alias ) in the address book. They are ‘People’ views. We also have many ‘Location’ forms. Is it okay? Are Aliases not suppossed to unique?

Thanks

Subject: It’s a bug in the template.

Lotus left a bunch of duplicate elements in the 6.5 / 6.0.3 template. I haven’t noticed it being a problem.

Subject: Duplicate design elements in Addressbook

Nope. In fact, having multiple objects with the same alias is a useful design tool. Any given design element can be hidden from the web, Notes clients, and mobile clients. If you make elements with the same alias but hide them in different contexts, the appropriate one will appear in appropriate context. What this means is that you can have one form for use in a Notes client and a completely different one for web use without having to clutter up your designs with a combination of LotusScript actions, JavaScript, pass-thru HTML and so on and worry about what gets hidden in which environment. You can put all the Notes stuff on one form and all the web stuff on a different form. Neat.

Subject: RE: Duplicate design elements in Addressbook

They are not set to ‘hide from web’ or notes client. When a view’s name and alias is same then which view will the formula pickup when I use them in the @picklist? The design of these duplicates is different too! One people have more columns than the other.

Subject: RE: Duplicate design elements in Addressbook

My experience is that the first one in the design view is the one the server finds, but others disagree; saying that it’s based on NoteID, which boils down to chronological order of creation.

Subject: Duplicate design elements in Addressbook - replication conflict?

I think that in Notes 6.x you sometimes get duplicate design documents when you have a replica conflict.