Control binding is not supported Error after adding Filter to Secondary Datasource Value - InfoPath Dev
in

InfoPath Dev

Control binding is not supported Error after adding Filter to Secondary Datasource Value

Last post 09-22-2011 03:42 AM by Beircheart. 0 replies.
Page 1 of 1 (1 items)
Sort Posts: Previous Next
  • 09-22-2011 03:42 AM

    Control binding is not supported Error after adding Filter to Secondary Datasource Value

    Hi,

    I have created a Browser enabled form in Infopath 2010. I have a drop down list on my main view that pulls from a secondary datasource using one secondary datasource field as a value and another as a display name. This works fine

    Now, when I try to display this as a calculated value in a Print View, I get the "Control binding is not supported" error. I understand what the error is telling me so now I'll explain the part I don't understand

    I've tried setting 2 different values in my Calculated Value control:

    (1) xdXDocument:GetDOM("Faculties")/dfs:myFields/dfs:dataFields/tns:FacultiesResponse/tns:FacultiesResult/Faculties/Faculty/DOM_NAME[../DOM_CODE = xdXDocument:get-DOM()/my:ProgrammeForm/my:Descriptors/my:HostFaculty]

    (2) xdXDocument:GetDOM("Faculties")/dfs:myFields/dfs:dataFields/tns:FacultiesResponse/tns:FacultiesResult/Faculties/Faculty/DOM_NAME

    Using value (1), I get the control binding error, however if I set the Calculated Value control to value (2) (i.e. Remove filter) then the error disappears... This doesn't make sense to me because when a filter is included it should return less values and in my case, it will return 1 so why would the filter trigger the error? Is this simply a bug or am I missing something? If it is a bug, what's the best route to report it?

    And another thing that makes me think it's just a bug, is that at one point the value sown in (1) worked without error. This was after a series of removing, adding the control and opening and closing the form

    Also, I realise that I can just put an instance of the drop down in the Print View instead and that would display the Display Name value (Albeit with that *** of an underline)

    So after all that disjointed rambling, I'm asking: Has anyone experienced this before? Is the error really just a bug? Is there a way around it? If it is a bug, what's the best way to report it?

    Thanks in advance,

    Ben

Page 1 of 1 (1 items)
Copyright © 2003-2019 Qdabra Software. All rights reserved.
View our Terms of Use.