We have roaming pnabs on a user’s mail server, and a replica on a clustered server, and of course there is the local replica on a user’s client. Thus we have three replica pnabs in our environment.
I have created a new template using the “StdR4PersonalAddressBook” template and created a new field in the contacts form. It is a editable combobox field called “IAVisibility”, with the following as the list values…
Add to Firm List|IA Firm
Not in Firm List|IA Personal
It has a default value of … @If(@IsNull(IAVisibility);“IA Firm”;IAVisibility)
This field is using hide/when based on an ACL role. We turn on ECA on for the roles to work.
There is also a few new columns in the contacts view that work with this new field.
Here is the issue…
I replace the design of a user’s pnab, on their mail server, with this new pnab template. I set the role so the the field and the view columns are visible.
When the user replicates, the new design with the role settings come down. The default values for this field, based on the formula above, is “Add to Firm List”. The user will open an existing document and set the “IAVisibility” to “Not in Firm List” if the user wishes to do so.
Given a little time for replication, the user gets replication conflicts.
Where are these conflicts coming from? Is it the clusted replicas? Is it the use of Null? For the life of me, I can’t see how replacing a design and having a user make a change from default to the other choice will cause a replication conflict. I am using Null because some pnabs may be using a different template that uses IAVisibility field and may have a Null value. Depending on the situation, we may replace the design with the new template and need to catch the null value if it exists.
But if I replace right from the standard pnab template, would the null as part of default make a difference?
Please help!!