Just encountered the issue where if you try to create a data source on an XPage and the source is a form that contains subforms, you can’t see the listing of the fields in order to bind controls to them.
Does anyone know the status of this or are there any workarounds that don’t involve removing the subforms from the form?
Many thanks
Melissa
Subject: fixed in 852
can’t remember if it was fixed in a FP or not, I’ll check on that.
If memory serves, this happens if the subform has an alias - subforms without aliases would be ok. So you could temporarily remove the alias from the subform to get around. And I know this is not ideal, but you can always type in any field name to the data source binding (though that isn’t nearly as nice a UI!)
Subject: Thanks for the prompt response!
Was typing in the field names but taking a while…

Subject: apparently the fix was ultimately not included in a fix pack 
so 8.5.2 will be what you want 
Subject: Edit your XPage in the Source tab…
- Then you may put in whatever fields you like. If you are unsure how to put a new field in, then use the Design tab to drop in one of each type you want to use, with any sort of data binding, then copy and paste that XML in the Source tab as required. When the XPage renders it will bind correctly, and it’s orders of magnitude faster than the zillion-click Design tab.
Hope this helps…