C1FlexReport: Legacy subreport field broken in .664

Posted by: wknauf on 7 August 2024, 3:35 pm EST

    • Post Options:
    • Link

    Posted 7 August 2024, 3:35 pm EST

    Hi C1,

    it seems the most recent version broke the legacy subreport fields.

    Attached is a sample, but it is a bit difficult to reproduce the issue: the reports must use SQL statements so that the error occurs.

    So, create a SQLServer database and execute the script “Reportdata.sql”.

    Then modify the connection strings for the two reports in “VAKalkulationEinzelaufstellung.flxr” and replace “PASSWORD”, “LOGIN”, “DATABASE” and “DATASOURCE”.

    When executing the sample (click the “Load report” button), you will see that the sub report is not rendered, the result has only two lines of text.

    With 8.0.20233.636, it works.

    FlexSubReport.zip

    It seems to be related to the legacy subreport field - the flxr was originally converted from a C1Report xml file and is ages old.

    This is the broken field:

    <Field>
      <Name>Field3</Name>
      <Section>Detail</Section>
      <SplitVertBehavior>KeepTogether</SplitVertBehavior>
      <Left>75</Left>
      <Top>645</Top>
      <Width>8955</Width>
      <Height>315</Height>
      <AutoHeight>GrowAndShrink</AutoHeight>
      <Subreport sys="string">Termine</Subreport>
    </Field>

    If I just replace “Field” by “SubReportField”, it works:

    <SubreportField>
      <Name>Field3</Name>
      <Section>Detail</Section>
      <SplitVertBehavior>KeepTogether</SplitVertBehavior>
      <Left>75</Left>
      <Top>645</Top>
      <Width>8955</Width>
      <Height>315</Height>
      <AutoHeight>GrowAndShrink</AutoHeight>
      <Subreport sys="string">Termine</Subreport>
    </SubreportField>

    Note: in this sample, there is a no filter expression. If others are hit by the same problem, they also have to convert the filter expression that was original stored in the “Text” child element, to something like this:

    <SubreportFilter>
      <Expression>...</Expression>
    </SubreportFilter>

    The element

    <Calculated>true<Calculated>

    should be removed in this situation.

    So, we have to convert all old Fields to “SubreportField”, and hopefully the issue is solved for us.

    Best regards

    Wolfgang

  • Posted 8 August 2024, 5:45 am EST

    Hello Wolfgang,

    Thank you for reporting the behavior with such detailed steps. We were able to observe it on our end as well.

    We have escalated it to the development team to get their insights. Rest assured, we’ll update you once we get any necessary information.

    [Internal Tracking ID: C1WIN-32768]

    Regards,

    Uttkarsh.

  • Posted 9 August 2024, 6:09 am EST

    Hello Wolfgang,

    As per the developers, the ETA for the fix is 2024 v1 hotfix 2.

    Rest assured, we’ll update you once the fix is available.

    Regards,

    Uttkarsh.

  • Posted 25 October 2024, 8:01 am EST

    Hello Wolfgang,

    The issue has been fixed in 2024 v1 hotfix 2.

    You can download the latest version (8.0.20241.672) of C1 to resolve the issue.

    Regards,

    Uttkarsh.

  • Posted 28 October 2024, 3:30 am EST

    Thanks, I can confirm that it works now.

    Best regards

    Wolfgang

Need extra support?

Upgrade your support plan and get personal unlimited phone support with our customer engagement team

Learn More

Forum Channels