Loading...

error with CAML query in qDiscussionView

error with CAML query in qDiscussionView

Home Forums QuickApps Forum error with CAML query in qDiscussionView

  • This topic is empty.
Viewing 8 reply threads
  • Author
    Posts
    • #5061
      Anonymous
      Anonymous
      Participant

      Hi Kate,

        Please ensure that you use the CAML filter builder interface to build the filter condition.

      If you still see the issue please provide the list template and the qDiscussionView web part template.

    • #6114
      Anonymous
      Anonymous
      Participant

      , I did post these to my earlier reply…thought that you would have been notified but guess it didn't work that way.  any insight you might provide is most appreciated! Thanks, Carrie

    • #6369
      Anonymous
      Anonymous
      Participant

      Hi Carrie,

        Let's do the following test, remove everything except the confidential variable and see if that works.

      To ensure that we don't break the XML please use the builder to do that.

      Also, please remember that the session variable name is case sensitive and check the docuemntation to ensure that the value type, source name asre used correctly.

    • #6370
      Anonymous
      Anonymous
      Participant

      The confidential condition does work on its own. The other piece works on its own too…it’s when they are put together that I get the error

    • #6112
      Anonymous
      Anonymous
      Participant

      Please see attached.  I used the CAML and receive an error "Cannot complete this action. try again"

      This works:

      viewcaml.jpg

      Anca wrote:

      Hi Kate,

        Please ensure that you use the CAML filter builder interface to build the filter condition.

      If you still see the issue please provide the list template and the qDiscussionView web part template.

      Need to add a select to include when “Confidential” = No.

      confidential caml.jpg

      Receive this error upon return to the page

      error.jpg

    • #6113
      Anonymous
      Anonymous
      Participant

      Hi Carrie,

        Unfortunately the screehots you attached can't be seen.

      Would you mind to re attach them.

      Thank you,

    • #6371
      Anonymous
      Anonymous
      Participant

      Let's try to change the condition, I assuma that is an AND between those conditions, please make it OR to see what happens.

      PS

      What's your Quest Web Parts and SharePoint version?

    • #4299
      Anonymous
      Anonymous
      Participant

      This following CAML query is the one currently being used and is working fine:

        

        <Or>

          <Eq>

            <FieldRef Name=”ExtCustNum” />

            <Value Type=”Text” Source=”Session” SourceName=”SourceNameAlpha” SessionName=”TWSearchSession” />

          </Eq>

          <Contains>

            <FieldRef Name=”ExtCustNum_x003a__x0020_Cust_Nam” />

            <Value Type=”Note” Source=”Session” SourceName=”SourceNameSearch” SessionName=”TWSearchSession” />

          </Contains>

        </Or>

        

      We are trying to extend it with the confidential variable as well like this (this is the one that fails):

      <And>

        <Eq>

          <FieldRef Name=”Confidential” />

          <Value Type=”Boolean”>0</Value>

        </Eq>

        <Or>

          <Eq>

            <FieldRef Name=”ExtCustNum” />

            <Value Type=”Text” Source=”Session” SourceName=”SourceNameAlpha” SessionName=”TWSearchSession” />

          </Eq>

          <Contains>

            <FieldRef Name=”ExtCustNum_x003a__x0020_Cust_Nam” />

            <Value Type=”Note” Source=”Session” SourceName=”SourceNameSearch” SessionName=”TWSearchSession” />

          </Contains>

        </Or>

      </And>

      qDiscussionView error.PNG

      QWP 5.6

    • #6372
      Anonymous
      Anonymous
      Participant

      Receive the error 'cannot complete this action, please try again'.  web part version is 5.6 and SharePoint is 2010. See attached

Viewing 8 reply threads

You must be logged in to reply to this topic.