We're investigating this problem now, and of course support will be in contact about the PMR. I will follow up here if we find a workaround.

Thanks for your patience.

Can you try validating your CQ schema in the Designer? If there are any errors or warnings, fixing them might work around this problem.

- Thanks, Sam

We may have found a workaround for this problem.

The issue appears to be a problem with a list view control on a form. Somehow, the "Field Name" (or "Source Field") property for a list view's column header is being being removed from the schema. The fix is to set a value for the column header's "Field Name" property.

You can do that by following these steps:

1. In CQ Web, attempt to create a new record for ALL record types in your schema, even those not used by your RQM/CQ integration.

2. Note if any record types return a server 500 error instead of displaying the create record dialog.

3. For the record types that return a server 500, view their forms in CQ Designer.

4. For those forms in question, inspect all list view control column headers and verify they have a "Field Name" (or "Source Field", if you're using the Eclipse based CQ Designer) value. If they do not, specify a value.

5. Save the schema, apply it to your database, clear browser cache, and try again.