property COUNT ignored on table and pager by result with transpose

[sbsbb]

I have this on two views now, not sure if it is a problem on Sideview :

I have a postprocess, that is making a search, ending with a | transpose
Doesn't matter what I am setting under "count" by table and/or pager object, the table display always 10 rows...
I can't set it to 3 or 15.
(If there is more than 10 results, pager is working fine, and making more pages)

Hi, here are the code for one of the views.
- I can't test the without transpose, because in that case, it return only 1 row...
- I'm encountering this problems only on views with a search with transpose.
- I use the version 2.4.7 (April 15th 2013) of sideview

<view isSticky="False" isVisible="true" onunloadCancelJobs="true" template="dashboard.html">
  <label>Vergleich EinfahrtEreignis </label>

  <module name="AccountBar" layoutPanel="appHeader" />

  <module name="AppBar" layoutPanel="appHeader" />

  <module name="SideviewUtils" layoutPanel="appHeader" />

  <module name="Message" layoutPanel="messaging">
    <param name="filter">*</param>
    <param name="maxSize">2</param>
    <param name="clearOnJobDispatch">False</param>
  </module>

  <module name="HTML" layoutPanel="viewHeader">
    <param name="html"><![CDATA[
        <h1>Alle CUS Meldungen</h1>

]]></param>
  </module>

  <module name="URLLoader" layoutPanel="viewHeader">

    <module name="TimeRangePicker" layoutPanel="panel_row1_col1" autoRun="True">
      <param name="default">Last 60 minutes</param>
      <param name="searchWhenChanged">False</param>

      <module name="Pulldown">
        <param name="float">left</param>
        <param name="label">Plattform</param>
        <param name="name">plattform</param>
        <param name="staticOptions">
          <list>
            <param name="selected">true</param>
            <param name="value">t_kihub</param>
            <param name="label">test</param>
          </list>
          <list>
            <param name="value">i_kihub</param>
            <param name="label">inte</param>
          </list>
          <list>
            <param name="value">p_kihub</param>
            <param name="label">prod</param>
          </list>
        </param>

        <module name="Search">
          <param name="search">
| dbquery $plattform$-kihub "SELECT ABK,BEZEICHNUNG_OFFIZIELL FROM KIHUB_STAMMDATEN.BP WHERE LANDUIC=85 ORDER BY BEZEICHNUNG_OFFIZIELL " limit 1000
</param>

          <module name="Pulldown">
            <param name="labelField">BEZEICHNUNG_OFFIZIELL</param>
            <param name="valueField">ABK</param>
            <param name="postProcess">$postProcess | sort BEZEICHNUNG_OFFIZIELL</param>
            <param name="float">left</param>
            <param name="label">BP</param>
            <param name="name">bp</param>
            <param name="staticOptions">
              <list>
                <param name="selected">true</param>
                <param name="value">*</param>
                <param name="label">*</param>
              </list>
            </param>

            <module name="Button">
              <param name="allowAutoSubmit">False</param>

              <module name="Search" layoutPanel="panel_row2_col1" group="CUSM Left Join VDV">
                <param name="group">CUSM Left Join VDV</param>
                <param name="search"><![CDATA[
index=$plattform$ sourcetype=cus-messages H_messageType="CUSM_EinfahrtEreignis" H_BP_ABK=$bp$ | fields + H_*,xml | head 100 |  spath input=xml output=BPUIC path=ns3:CUSM_EinfahrtEreignis.MeldungsKopf.Meldung.Bp.ns2:BPUIC | eval FahrtBezeichner=(H_TU + "-" + H_trassenID) |  convert ctime(_time) as CUSM_time | rename xml as cus_xml |  join overwrite=true type=left FahrtBezeichner [search index=$plattform$ eventtype=cus5-vdv-messages dienst=ans resource=datenabrufen.xml | fields + xml | spath input=xml output=zbn  path=DatenAbrufenAntwort.Zubringernachricht | mvexpand zbn | spath input=zbn | search ASBFahrplanlage.AufASB=false |rename ASBFahrplanlage.FahrtID.FahrtBezeichner as FahrtBezeichner  |  convert ctime(_time)  as VDV_time | rename ASBFahrplanlage.ASBID as ASBID | eval BPUIC=substr(ASBID,2)]  | table *





































]]></param>

                <module name="JobProgressIndicator">

                  <module name="Pager">

                    <module name="Table">
                      <param name="fields">CUSM_time,FahrtBezeichner,H_BP_ABK,VDV_time,ASBFahrplanlage.AufASB</param>

                      <module name="PostProcess" layoutPanel="panel_row3_col1" group="CUSM_EinfahrtEreignis">
                        <param name="group">CUSM_EinfahrtEreignis</param>
                        <param name="search"><![CDATA[
| search FahrtBezeichner=$row.fields.FahrtBezeichner$ | table cus_xml | spath input=cus_xml output=cm path=ns3:CUSM_EinfahrtEreignis.VmEreignisInfoKurz | spath input=cm | fields - cm, cus_xml | transpose






]]></param>

                        <module name="Pager">
                          <param name="count">25</param>

                          <module name="Table">
                            <param name="count">40</param>
                            <param name="hiddenFields">cus_xml,cm</param>
                          </module>
                        </module>
                      </module>

                      <module name="PostProcess" layoutPanel="panel_row3_col2" group="VDV ZubringerNachricht">
                        <param name="group">VDV ZubringerNachricht</param>
                        <param name="search"><![CDATA[
search FahrtBezeichner=$row.fields.FahrtBezeichner$ | table VDV_time,ASB* | transpose

]]></param>

                        <module name="Pager">
                          <param name="count">3</param>

                          <module name="Table">
                            <param name="count">3</param>
                            <param name="hiddenFields">cm,cus_xml</param>
                          </module>
                        </module>
                      </module>
                    </module>
                  </module>
                </module>
              </module>
            </module>
          </module>
        </module>
      </module>
    </module>
  </module>
</view>

[sideview · Accepted solution]

The only thing I can think of, is that you have a 'Count' module, or a 'Pulldown' configured with a name of results.count, and it's sitting upstream from both the Pager and the Table. In that case the count pulldown is supposed to override the count params on both Pager and Table.

Can you post the XML for one of the two views? Also let me know what version of Sideview Utils you're on (You used the app-tag of the really old 1.3.5 version). Also let me know if the problem is only when you use the transpose command; I will assume it's not. Overall I'm afraid I can't reproduce any problem here so hopefully you can give me more information about what you're seeing.

UPDATE:

Thanks for the heads up. It is a bug, I have fixed it and the fix will be in the next release. What happens is that both the Pager and Table (and Paginator and SimpleResultsTable) modules can either set their count param themselves, or they can receive it from upstream. If they both set it and receive it from upstream, the upstream value will win. eg: an upstream value might be coming from a Count module or a Pulldown set with 'name' of 'results.count', either of which would be the control the user used to choose the number of rows per page.

The problem is that the table modules let the results.count key continue downstream to where it will affect the second tier and lower tiers of drilldown tables.

There's a workaround, and that's to insert a ValueSetter module downstream from the first Table, and upstream from the second Pager, and set the count that way:

<module name="ValueSetter">
  <param name="name">results.count</param>
  <param name="value">3</param>

and you might as well remove all of the countparams on the downstream Pager and Table modules because they will be getting ignored.

Or you can wait until the next Sideview Utils release where this bug is fixed. Note that even then - your config is sprayed liberally with count params and the count params on Table will always be overridden by the count params on the Pager that directly contains them....

Other minor problems I noticed.

• you need a closing "$" character on your $postProcess token here. The unclosed $ token will cause the entire postProcess param to be effectively ignored.
  <param name="postProcess">$postProcess | sort BEZEICHNUNG_OFFIZIELL</param>

• I recommend using the Pulldown's template param instead of having the field="" part in the searches. eg <param name="template">index=$value$</param> then with just $platform$ in the searches/postprocesses. There is a docs page in the Pulldown section speaking to just the template param and why it's a good thing.

[sideview]

=/ Fixed 2.4.9, released May 24th 2013

Fixed a minor bug with paged tables where if you nested one inside another, any count param from the outer set would overrride all count params you had on the inner set. Fix applied to both Table and SimpleResultsTable.

Full release notes are here http://sideviewapps.com/apps/sideview-utils/release-notes/

Sorry I don't always remember to update answers posts when the bugs get fixed. But there is a mailing list you can sign up for ( http://sideviewapps.com/apps/sideview-utils/mailing-list/ to get sent release notes when a new version is released.

[sbsbb]

Hi, Any update on this ? I'm still experiencing that problem, would it be possible to fix it in the code ?

[sbsbb]

I've updated my post, with the information you asked for... thanks.