Fill Parameters in P & D with the right Table / Table identifier when printing a draft document Completed

Daniel Schmidt - neumeierAG

Hello,

we´ve made a Crystal Report, which works with draft documents and normal documents.
Therefore we setup the [@BOY_85_BASECONFIG] - Table with "Allow Draft Printing" = 'Y'.
Also did we change the filling of the Parameters $[BOY_TABLE] AND $[BOY_TABLE_IDENTIFIER] in the crystal report definition with a sql-query which looks on the status of the report given by the UI:

SQL:SELECT CASE WHEN '$[$81.0.0]' = '6' THEN 'ODRF' ELSE '$[TABLE]' END FROM DUMMY
SQL:SELECT CASE WHEN '$[$81.0.0]' = '6' THEN 'DRF' ELSE '$[TABLE_IDENTIFIER]' END FROM DUMMY

The problem with this logic is, that $[TABLE] AND $[TABLE_IDENTIFIER] are not set to the right tablenames while using the massdelivery or the B1UP ServerComponent.
So we always have to make a second Crystal Report Definition for the customers, which are using massdelivery or the B1UP ServerComponent for printing/mailing documents.

It would therefore be very nice if we wouldn´t have to make sql-statement to choose whether ODRF/DRF or the name of the responsive tables are selected for these two parameters.

So when the document ist draft :

$[BOY_TABLE] should be "ODRF"
$[BOY_TABLE_IDENTIFIER] should be "DRF"

When document is a regular addedd document (AR_ORDER):

$[BOY_TABLE] should be "ORDR"
$[BOY_TABLE_IDENTIFIER] should be "RDR"

Thanks for your feedback.

Comments

2 comments

Date Votes
  • Comment author
    SSP Automation
    Thank you for your request. It has been scheduled for review by the development team that will get back to you should there be questions.
    (Please note that as we are user-driven we can't guarantee that your request will be met unless it gets many votes and/or fit the product vision)
    Read more about the Feature Request process here
    [Internal Id: 48772]
    0
  • Comment author
    Rasmus Jensen

    Will be included in B1UP 2021.10

    0

Please sign in to leave a comment.