Schedule Builder Field Type Not Working on Attribute Matrix

[billdeitrick]

Please go through all the tasks below

• Check this box only after you have successfully completed both the above tasks

Please provide a brief description of the problem. Please do not forget to attach the relevant screenshots from your side.

The Schedule Builder field type is not working properly when used as part of an attribute matrix. It doesn't appear to save values, and it also seems to wipe other fields in the matrix when the schedule editor dialog is opened. This is occurring on plugin release 1.0.8.16 on Rock v16.10.

Expected Behavior

The Schedule Builder field should work as expected when used in an attribute matrix.

Actual Behavior

The Schedule Builder field doesn't save values and opening the dialog box to edit the schedule can erase the contents of other fields.

Steps to Reproduce

1. Create an attribute matrix template with a text attribute and a schedule builder attribute.
2. Create a simple workflow with a form using the matrix template as the only field.
3. Fill out the form. Note the schedule is not saved. Also note that typing a value in the text field, then opening the schedule builder dialog wipes the value in the text field.

Video demonstrating the issue is available below:

2025-05-19_16-24-50.mp4

I can confirm this was working with previous Rock versions and previous versions of the Workflow Extensions plugin.

Rock Version

16.10

Plugin Version

1.0.8.16

Client Culture Setting

en-US

[billdeitrick]

This may be related to a core bug:

SparkDevNetwork/Rock#6175

SparkDevNetwork/Rock@10fbce7#diff-722b903d8cf4da3162cd440e5dfd0250928ca68a70e6e68a380a1b7fd03d6a7b

[tcavaletto]

Testing this in 17.0 to see if core fixed the issue has opened the door for a bunch of issues: Namely, the attribute matrix template detail page is now obsidian. The Schedule Builder is not an obsidian control, so it doesn't show up. While we can map most list and item tree controls to a universal field type, this one is complicated enough that I think for now we need to stop using it / Let people know it only works in webforms

[frogydiak]

This issue is partly related to the one posted about Select Extended with regard to Obsidian Matrix Template Detail Page mentioned by @chead4 from SparkDev team.