Hi, In “VendTable” ,i want to have validation for the Addresses entered. (i.e) in Address tab when a vendor enters a address (for example say the address be “Address 1”), no other vendor should enter the same address.If he enters the same address,it should prompt a error. how to do? Regards Rajee
In vendTable form per each vendor can have multiple address.
For your Req , U can try with Address Table Realation
You can use Global address book reject duplicate functionality in Basic>Setup>GAB. and mark reject duplicate as per your requirement in Parameter.
“Cannot create a record in Party address mapping (DirPartyAddressRelationshipMapping). Company: gind. The record already exists.” WHEN I TRY TO SAVE A RECORD IN ADDRESS TAB IN THE “VENDTABLE” ,I GET THIS ERROR…I HAV’NT CHANGED ANYTHING .BUT I GET THIS ERROR
Kindly help me to solve this issue.“Cannot create a record in Party address mapping (DirPartyAddressRelationshipMapping). Company: gind. The record already exists.” WHEN I TRY TO SAVE A RECORD IN ADDRESS TAB IN THE “VENDTABLE” ,I GET THIS ERROR…I HAV’NT CHANGED ANYTHING .BUT I GET THIS ERROR
If an address for instance A1 is meant only for vendor V1. if this is the requirement have a field called as used by in the dirpartytable. Use the field to keep vendor information if the address is inserted. If any other vendor tries to use the same address have a validation error thrown and do not allow to store the address. ( the later part needs to be done on address relation mapping table)
Hi Parthav,thanks for the suggestion.Is there anyother way to do the same…without adding a field?
The error is becuase of in the Tables - DirPartyAddressRelationshipMapping having the duplicate records basing on the PartyAddressRelationshipRecId beacuse in t\abel level it is unique index…
Once check in this whether any duplicate records exists.
U can use search criteria on DirParty Address mapping table. The records should be unique for a party id. i.e. a address record (address.recid) could be associated with maximum one party id. You still need to use mapping table for validation. First solution was better if you can afford to use a field against address.
Yes naresh you are correct, there is duplication of "PartyAddressRelationshipRecId " in the table,because there are 5 different company’s and for all the 5 different company’s the adress gets created,if i created a address in one comapny… now how to solve?
In the Tables - DirPartyAddressRelationshipMapping there is index KeyIdx it doesnt allow the duplicate values basing on the fields PartyAddressRelationshipRecId,RefCompanyId.
So you are saying already the address got created with it when you try to create new it wont allow you…
yes you are right