Forum Discussion
luk Sorry for the delayed response. I'm seeing the same thing in my test community. I'm raising this with the Engineer who added the constraint.
I spoke with the Engineer who added the constraint.
I think the best way to address this is to file a Support ticket and call this out as a bug. We added the constraint and it is does not seem to be implemented in a way that a customer using the Community API could make use of it. The engineer wasn't able to provide a satisfactory workaround either.
EDIT: The Engineering team is planning to remove the 'node.id' constraint from the public documentation. If you feel that this is in error, definitely file a feature enhancement or a bug to pursue the issue. Having a customer on a ticket carries more weight.
Thank you for bringing it to my attention.
Related Content
- 2 years ago
- 4 years ago
- 3 years ago