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

Read/Write multiselect property

Former Member
Former Member
Guys, I again need your help. I'm going crazy with a (i think simple) problem, maybe you can help me out?
I've got a "onboarding" document, containing a multi-select property called "Department". It's a simple "choose from list Departments (multiselect).
At the And of the Onboarding, I create a Employee Object in the workflow and "copy" some of the onboarding property values. That works fine! I can copy text and single select (lookup).

What drives me crazy is to read a multiselect and write the same values to the "same" property in the new employee object.

I tried alot... at the moment i try it this way:

Read Multi-Select property

...
' Abteilung/Department
Dim ilookups_abteilung : set ilookups_abteilung = PropertyValues.SearchForProperty(1234).TypedValue.GetValueAsLookups
...


Write to the new object

...
' Abteilung
oPropVal.PropertyDef = 1234
oPropVal.TypedValue.SetValue MFDatatypeMultiSelectLookup, ilookups_abteilung
oPropValues.Add -1, oPropVal
...


That gives me a "type conflict"
What's the problem?
Regards
Chris
Parents
  • Making visual studio template only available to partners gives me same impression.


    I can definitely see that point of view, and it's a discussion that I've had with a number of people. I personally feel that it would not be professional of us to provide the VSIX across to end-users without having a support network in place in case they have issues. You have to remember: when this was originally published, we didn't have the developer portal or any other supporting resources for end-users.

    As we move forward and the amount of public content for the VAF grows, we may feel more comfortable with publishing this more widely, but we (currently) do ask that the VSIX is obtained through your partner or account manager at M-Files. This allows them to discuss with you what support they can provide. I know that we have a number of larger (or more technical) end users that have been given access to the VSIX through their partners and are actively developing solutions. I - again, personally - have no issue with this, provided you - as an end-user - have some support network in case of issues.

    Regards,

    Craig.
Reply
  • Making visual studio template only available to partners gives me same impression.


    I can definitely see that point of view, and it's a discussion that I've had with a number of people. I personally feel that it would not be professional of us to provide the VSIX across to end-users without having a support network in place in case they have issues. You have to remember: when this was originally published, we didn't have the developer portal or any other supporting resources for end-users.

    As we move forward and the amount of public content for the VAF grows, we may feel more comfortable with publishing this more widely, but we (currently) do ask that the VSIX is obtained through your partner or account manager at M-Files. This allows them to discuss with you what support they can provide. I know that we have a number of larger (or more technical) end users that have been given access to the VSIX through their partners and are actively developing solutions. I - again, personally - have no issue with this, provided you - as an end-user - have some support network in case of issues.

    Regards,

    Craig.
Children
No Data