Wcm_placeholder service pulls content with default template

Question

I have mutiple templates defined for a region definition in the placeholder definition. When accessing content using wcm_placeholder service it always pulls content usign the default template even if the content has been setup to use a different region template.
I calling the page using the format below
http://ecm/idc/idcplg?IdcService=WCM_PLACEHOLDER&dataFileDocName=RVI_DATA_GIZMOS&placeholderDefinitionDocName=PH_MAIN
Any ideas why this is happening? is this a bug with the service that it doesn't know which template to use even if it is defined at the content level?
Thanks!

Answer 1

Now I understand what you're looking to do, but unfortunately, that's not possible because when you associate a piece of content to use a specific region template, it is stored as a section property, not as content metadata. To take it one step further, it can either be the primary or secondary page of that section.
For instance, if you click on the section in Designer, you'll see something like:
Primary Page Params: [placeholderName]=RVI_DATA_GIZMOS
Primary Page Region Templates: [placeholderName]=[RegionTemplate]
You can easily have RVI_DATA_GIZMOS be the primary page of another section, and still use a different region template. So the WCM_PLACEHOLDER service has no idea which to use, and therefore has to use the default.
In the end, it sounds like the WCM_PLACEHOLDER service should probably take two additional parameters, nodeId and isSecondaryPage, in order to give what you need.