Smart field problem
We are trying to build a data definition with repeating parts and we find that the settings on one group affects the values on the repeats (text and screenshots of an example follows). Is that as designed?
We would have thought that a each group would be
independent.
Thanks,
David
===== Example
If 'Hours Type' was a direct child of 'Hours', I would expect the show/hide feature to affect all the child 'Hours Group'; however since it's a child of 'Hours Group', I would think it shouldn't affect what's listed in other 'Hours Group' nodes. See below example.
When both 'Hours Type' fields are set to 'Days Range, only the 'Days Range' picker appears.
However, when the second 'Hours Group' node has 'Hours Type' set to 'Days Individual', you will note that both 'Days Individual' and 'Days Range' are showing on both Hours Group nodes, regardless of what is selected in that specific node.
- example1.png 44.2 KB
- example2.png 52.4 KB
Discussions are closed to public comments.
If you need help with Cascade CMS please
start a new discussion.
Keyboard shortcuts
Generic
? | Show this help |
---|---|
ESC | Blurs the current field |
Comment Form
r | Focus the comment reply box |
---|---|
^ + ↩ | Submit the comment |
You can use Command ⌘
instead of Control ^
on Mac
Support Staff 1 Posted by Tim on 08 Apr, 2014 08:42 PM
Hi David,
It sounds like you're running into this known issue. We're hoping to have this fixed for the 7.10.1 patch release which may be available in a few weeks assuming testing/QA goes as planned.
Apologies for the inconvenience! Let me know if you have any further questions.
Thanks
2 Posted by Ryan Griffith on 14 May, 2014 07:03 PM
Hi David,
Great news, Cascade Server 7.10.1 is now official and can be downloaded by visiting our downloads page. In this release is a fix for smart field inheritance, which should definitely help out your situation.
Please let me know if you have any questions.
Thanks!
Ryan Griffith closed this discussion on 05 Jun, 2014 12:41 PM.