on 09-21-2006 3:41 PM
Hi, due to characteristics of our implementation we need a qualified table for mails. The standard one can be used but i have a problem, i need a restriction for avoiding duplicated records and for now, i´ve not got the right key.
I.E.
ADDRESS TYPE: non qualifier. Unique field
MAIL TYPE: Qualifier . Unique field.
mail address: qualifier.
I need to get the structure below with one record for value like this:
add type:
Standard
KEY1
aaa@hotmail.com
but if trying to create a new record with the same keys but with the different mails it succedes thing that it´s what i don´t need. Does anyone know how to fix those values, i can´t have any duplicates and i can use other table type as needs to be syndicated as qualified.
Thanks in advance.
Antonio,
You cannot restrict duplicate records in a Qualifier table.
If you define a Unique field in a Qualifier table.
Uniqueness is applied to the entire records in a Repositary not for a Perticular record qualifier values.
If you are using portal you can implement this in UI not in the data manager.
Thanks,
Madhu
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Antonio - Have one quick question on your question...to understand it better..
do you mean to say that you are creating records like the following...
Ex1 :
Standard,Key1,aaa@hotmail.com
Standard,Key1,bbb@hotmail.com
or Ex2 :
Standard,Key1,aaa@hotmail.com
alternative,Key1,bbb@hotmail.com
or Ex3:
Standard,Key1,aaa@hotmail.com
Standard,Key1,aaa@hotmail.com
which one of the above examples is ok and which one is not.
Cheers,
Aravind
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
85 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.