Options
  • State Verified Answer
  • Locked Locked
  • Replies 10 replies
  • Subscribers 8 subscribers
  • Views 1163 views
  • Users 0 members are here
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

A duplicate property value [PropertyName] was encountered error

gdaymate

Hello everyone!

Today I stumbled upon an odd error. Couldn't really figured out what's wrong. So I have a VAF running in my vault during Before Create New Object Finalize event handler.

The script meant to set properties before the object is created. The first run after deployment is smooth sailing. However, on the second object creation and so on, it threw an error "A duplicate property value [PropertyName] was encountered". I double checked the variable returns only one value not multiple. Below is the snippet on how I set the properties after getting the data from the searching. Is this a known issue or a bug? Or perhaps I should add something to the script?

var oResults = env.Vault.ObjectSearchOperations.SearchForObjectsByCondition(oSc, true);
int theobjID = 0;               

                if (oResults.Count > 0)
                {
                    
                    foreach (ObjectVersion routing in oResults)
                    {
                        if (routing.ObjVer.Type == 101) 
                        {
                            theobjID = routing.ObjVer.ID;

                            break;
                        }
                        break; //to make it run only once 
                    }
                }
                

                var Remarks = env.Vault.PropertyDefOperations.GetPropertyDefIDByAlias("BP.PD.Remarks");
                aPropVal.PropertyDef = Remarks;
                aPropVal.TypedValue.SetValue(MFDataType.MFDatatypeMultiLineText, fData[4]);
                aPropVals.Add(-1, aPropVal);

                var TheGroup = env.Vault.PropertyDefOperations.GetPropertyDefIDByAlias("BP.PD.Groups");
                aPropVal.PropertyDef = TheGroup;
                aPropVal.TypedValue.SetValue(MFDataType.MFDatatypeLookup, theobjID);
                aPropVals.Add(-1, aPropVal);

                env.Vault.ObjectPropertyOperations.SetProperties(env.ObjVer, aPropVals);


Thank you in advance!

  • 0

    Might the properties collection already contain a value for one of these properties? How is it populated? 

  • 0 in reply to Craig Hawker

    What I don't understand is, why the first attempt of object creation has no issue and then the error starts appearing on the next attempt. The properties collection is totally empty from what I can tell. As you can see on the code snippet above that the data on the first PropertyValue is coming from an array and the second one is a lookup of an object id from the searching function.

  • 0 in reply to gdaymate

    Where do you create aPropVals? 

  • 0 in reply to Craig Hawker

    I created that at the very top outside of the function as a public variable. I added multiple PropertyValue like below but still getting the same error. 

    PropertyValue aPropVal1 = new PropertyValue();
var Remarks = env.Vault.PropertyDefOperations.GetPropertyDefIDByAlias("BP.PD.Remarks");
aPropVal1.PropertyDef = Remarks;
aPropVal1.TypedValue.SetValue(MFDataType.MFDatatypeMultiLineText, fData[4]);
aPropVals.Add(-1, aPropVal1);

PropertyValue aPropVal2 = new PropertyValue();
var TheGroup = env.Vault.PropertyDefOperations.GetPropertyDefIDByAlias("BP.PD.Groups");
aPropVa2.PropertyDef = TheGroup;
aPropVa2.TypedValue.SetValue(MFDataType.MFDatatypeLookup, theobjID);
aPropVals.Add(-1, aPropVal2);

  • +1 in reply to Craig Hawker

    I have solved the issue. The PropertyValues must be inside the function. Placing it as a public variable will trigger the error apparently.

  • 0 in reply to gdaymate

    You should be very careful with any public members. In general you should reduce the scope of everything to the minimum possible; in this case within the method.

    What's happening here is that the first object version populates an entry in the collection, then the second object version adds another for the same property definition. As a result there's then two entries in the collection.

    My rule of thumb: never use public members on your vault application class, and use other long-lived items (e.g. static) sparingly and only if you understand the consequence of doing so.

  • 0 in reply to Craig Hawker

    Well noted, Craig. Thank you for the reminder.

  • 0

    Hi all,

    I know this is a previous topic but just wondering on the scripting syntax.

    Based on the above scenario, understand that we have this property values aPropVals

    aPropVals.Add(-1, aPropVal2);


    Since we are using index -1, I am assuming that we are appending the value into this property values ?

    Is there any way we can remove all the values inside this property values ?

    I tried to perform below but it giving me parameter error ?

     

    aPropVals.Remove(-1)

  • 0 in reply to Thaqif Taher

    If you want to empty it then why not reinitialize it?

    aPropVals = new PropertyValues();

    Your remove code is throwing an exception because the items aren't actually added at index -1; each object is given an index > 0.  You would need to provide a valid index.

  • 0 in reply to Craig Hawker

    Hi Craig,

    Thank you for your assistance. Really appreciate it.





              

© M-Files Corporation 2024 | Privacy Policy