Announcement

Collapse
No announcement yet.
X
  • Filter
  • Time
Clear All
new posts

  • Isomorphic
    replied
    No extra properties are required, and in fact, normal fetches to populate a grid and export fetches work exactly the same way: first the data is retrieved and flattened, then the already-flattened data is deliver to the browser normally or turned into an export. So there doesn't really seem to be a way for the data flattening behavior of valueXPath to fail only for export.

    However, it looks like you've got a custom DataSource with quite a bit of custom functionality, so perhaps you've changed something important.

    If you need help figuring out what's wrong, please start by renewing your Support. Thanks.

    Leave a comment:


  • exportData functionality is not working as expected in SmartClient Ajax RIA system Version v12.1p_2021-05-18/PowerEdition Deployment (2021-05-18) when datasource field has value binding using valueXPath

    This is how it looks like in Our DataSource File
    <DataSource
    ID="dsID"
    serverConstructor="className"
    useMemoryPaging="false"
    gridResultsPerPage="1000"
    dbResultsPerPage="4000"
    useLabelService="true"
    exportReportDate="false"
    exportConstructor="ClassName"
    exportTitle="Adhoc Report"
    >
    <fields>
    <field name="title" type="text" title="Project Name" defaultDisplay="true" valueXPath="project/title"/>
    <field name="InspectionCountsTotal" fieldGroup="InspectionCounts" type="integer" defaultDisplay="true" labelCode="Label.Grid.InspectionCounts"/>

    </fields>
    </DataSource>

    As you notice we have two types of field , where for one we have direct mapping with DO and Other we did flattening of data using valueXPath, for bot types of fields, it display correctly on GRID

    but while exporting, it was not able to populate value for field which we have flattened data using valueXPath for example it displays value for project name in grid, but while exporting as excel it has blank for projectName for all row

    Do we need to add any extra property in datasource to support export functionality?
Working...
X