Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Potential issue with DepedentLookupFieldDefinition.ShowInDisplayForm #753

Closed
SubPointSupport opened this issue Dec 23, 2015 · 2 comments
Closed

Comments

@SubPointSupport
Copy link
Contributor

Hi! I ran across a "problem" today that I just want to raise here. I'm provisioning a DepedentLookupFieldDefinition using M2 1.2.40 CSOM. The field is added and so far all is good. BUT I also specified ShowInDisplayForm = false for that field, but that setting does not seem to work. Could that possible be because of lack of support using CSOM for that?

https://www.yammer.com/spmeta2feedback/#/threads/show?threadId=631884114&messageId=631884114

@SubPointSupport
Copy link
Contributor Author

Not all the fields properties were "promoted" for the DepedentLookupFieldDefinition. ShowInXXX props are some of these, they are not included into the provision, and M2 does not do a thing with them.

More coverage/test on all field props should be added to align the depended lookup field with regular fields.

@SubPointSupport SubPointSupport removed this from the 2016.02.08 milestone Feb 9, 2016
SubPointSupport added a commit that referenced this issue Apr 19, 2016
+ Potential issue with DepedentLookupFieldDefinition.ShowInDisplayForm #753
+ DependentLookupFieldDefinition: Id is not used #807
@SubPointSupport SubPointSupport modified the milestones: 2016.04.25, 2016.05.30 - DependentLookup May 26, 2016
@SubPointSupport
Copy link
Contributor Author

Implemented for SSOM/CSOM, handled by CanDeployRandom_DependentLookupFieldDefinition and changeable field (ExpectUpdate attr)

SSOM seems to support all props.
CSOM seems to not update the following props:

  • AllowMultipleValues
  • FieldType
  • LookupField

These field are excluded from the regression test validation. For the time being that seems to be a solution, as that set of the field is not actively used in the dependent lookup field provision scenarios.

Most likely, some kind of SharePoint CSOM API limitation. Further investigation will be required as per the customers feedback and valid provision cases to changes these fields.

SubPointSupport added a commit that referenced this issue May 30, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant