+3I inherited a project. When I moved the code from the Project Editor to my VS extension, I have an error regarding multiple keys.
This was apparently not a problem when the code was left in the project editor, but it is a problem in my VS extension library. Here is a snip so you can see the squiggles:
I don’t know if removing the IsKey from either field will cause a problem. Would it be safe to suppress the error with a comment?
Best answer by aleksandrsechin
Hi,
I don’t think it’s a good practice to keep a second IsKey when you already have IsKey together with the PXDBIdentity attribute. I would recommend the following: if you really need to keep the SlotID field, keep the IsKey on this field and remove it from SiteID.
Hi,
I don’t think it’s a good practice to keep a second IsKey when you already have IsKey together with the PXDBIdentity attribute. I would recommend the following: if you really need to keep the SlotID field, keep the IsKey on this field and remove it from SiteID.
+3Hi
+7
The general best practice is that you either have the identity field as a single key field, or a combination of any other fields as a key. But you should not do both since it leads to some nasty side effects.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
