Error 243 Properties cannot have the same priority while adding to the list

[Anonymous]

I have a coworker adding values to the list of values in a  custom property and he'll get an error 243 Properties Cannot Have The Same Priority while adding to the list. He can close vault, reopen and then continue with the edit

The server is 2018.1 while the client is 2017 

Here's the error message in the server log

24/10/2017 16:40:53 *******************************************************************
Error: Soap Exception ( mesg-id = 636444600535545091 )
Exception: PropertiesCannotHaveTheSamePriority [243]
Stacktrace:
Server stack trace:
at Connectivity.Core.BusinessLogic.PropertiesBL._SetMappingsToContentSourcePropertyDefinitions(IPropertyDefinition propDef, Int64 entClassId, ContentSourcePropertyDefinition[] csPropDefs, MappingTypeEnum[] mapTypes, Int32[] priorities, MappingDirectionEnum[] mapDirs, Boolean[] createNews, Boolean overwriteExisting, _setmappingsDelegate dataAccess)
at Connectivity.Core.BusinessLogic.PropertiesBL._SetMappingsToContentSourcePropertyDefinitions(IPropertyDefinition pdef, NormalizedPropertyMappings collatedClsMapsList, IEnumerable`1 deletedClasses, _setmappingsDelegate dataAccess)
at Connectivity.Core.BusinessLogic.PropertiesBL._SetPropertyDefinitionEntClassCtntSrcMappings(PropertyDefinition pdef, Boolean madeActive, List`1 clsMaps, Int64[]& contentSourceIds)
at Connectivity.Core.BusinessLogic.PropertiesBL.UpdatePropertyDefinitionInfo(PropertyDefinitionInfo propDefInfo, PropDefInfoDataEnum propDefInfoData)
at Connectivity.Core.Services.PropertyService.UpdatePropertyDefinitionInfo(PropertyDefinitionInfo propertyDefInfo)
at System.Runtime.Remoting.Messaging.Message.Dispatch(Object target)
at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg)

Exception rethrown at [0]:
at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
at Connectivity.Core.Services.PropertyService.UpdatePropertyDefinitionInfo(PropertyDefinitionInfo propertyDefInfo)
at Connectivity.Web.Services.v22.PropertyService.UpdatePropertyDefinitionInfo(PropertyDefinition propDef, EntityClassContentSourcePropertyDefinitions[] eClsCtntSrcPropDefs, PropertyConstraint[] constraints, Object[] listValues)
at SyncInvokeUpdatePropertyDefinitionInfo(Object , Object[] , Object[] )
at System.ServiceModel.Dispatcher.SyncMethodInvoker.Invoke(Object instance, Object[] inputs, Object[]& outputs)
at System.ServiceModel.Dispatcher.DispatchOperationRuntime.InvokeBegin(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage5(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage11(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.MessageRpc.Process(Boolean isOperationContextSet)

@Anonymousfor clarity @jason.courtemanche edited the original subject: Error when adding to the list of values

[cbenner]

@Anonymous

Can you also post a screen shot of the property definition itself?  And the mappings for it?

Take a look at this post by @ihayesjr.  Could this be part of it?

[Anonymous]

[ihayesjr · Accepted solution]

It is always recommended to do administrative changes in the same version of the client as the server you are connecting to. So the server is 2018, these changes should be done in a 2018 client. We place the following statement in our help.

It is not recommended that you administer Vault Settings or Global Settings using a client of a prior release version. Administration of Vault Settings and Global Settings should be done using an ADMS Console or Vault client of the same release as the target Vault server.

[Jason.Courtemanche]

Hi @Anonymous,

I am checking back to see if @ihayesjr post or @cbenner post helped you with your problem. Please add a post with how you decide to proceed and your results so other Community members may benefit.

Please hit the Accept as Solution button if a post or posts solve your issue or answer your question.

Regards,

Jason

[Anonymous]

The user claims they've not had any issues since moving to 2018

[Jason.Courtemanche]

Hi @Anonymous,

Thank you for following up and letting us know that the end user does not have the issue since using Vault Client 2018.

Regards,

Jason