• Replies 1 reply
  • Subscribers 337 subscribers
  • Views 90 views
  • Users 0 members are here
Related

Custom Order Confirmation

Kathleen Smith
$organization

Hi,

I'm working on custom order confirmations (in Infomaker) and am running into an issue when trying to print a confirmation from the print button in an order.  I receive the error 'retrieve argument 1 does not match expected type'.  My sql runs fine in SSMS,  and it works fine when I set it up and run it as a report (also works fine as an SSRS report, but alas, we can't use those as confs to be printed from the print order screen).  Any ideas?

Cheers,
Kathleen 

Parents
  • $organization

    Hi Kathleen,

    For this to work, the SQL SP and InfoMaker object need all the parameters used in the standard order acknowledgement - even though the only parameter required is the order number - passed back in the parameter @p_order_no.  Try looking for the SP called TP_ORDER_ACK.  For example, my SP starts off as: 

    CREATE procedure [dbo].[LRP_NIDA_ORDER_INVOICE] 
    ( @order_start_dt datetime = null,
    @order_end_dt datetime = null,
    @season_str varchar(255) = null,
    @perf_start_dt datetime = null,
    @perf_end_dt datetime = null,
    @mos_str varchar(255) = null,
    @reprint_ind char(1) = 'N',
    @list_no int = null,
    @mailing_dt datetime = null,
    @mailing_type varchar(8) = null,
    @signer int = null,
    @label_ind char(1) = null,
    @include_general_public char(1) = 'N',
    @eaddress_type int = null,
    @eaddress_purpose varchar(8) = null,
    @eaddress_market_ind_no char(1) = null,
    @report_type char(1) = 'A', -- 'A' for ack, 'C' for confirmation, 'O' for single order, 'B' for billing
    @p_order_no int = null,
    @habo_flag int = null, -- 1 = yes, 2 = no, 3 = all; only used for confirmations
    @exception_flag int = null, -- 1 = yes, 2 = no, 3 = all; only used for confirmations
    @ob_no int = 0,
    @balance_type int = 4 -- default is all orders; 1=no payment, 2=fully paid, 3=partially paid, 5=any balance due
    )

    Hope this helps!

    Martin 

Reply
  • $organization

    Hi Kathleen,

    For this to work, the SQL SP and InfoMaker object need all the parameters used in the standard order acknowledgement - even though the only parameter required is the order number - passed back in the parameter @p_order_no.  Try looking for the SP called TP_ORDER_ACK.  For example, my SP starts off as: 

    CREATE procedure [dbo].[LRP_NIDA_ORDER_INVOICE] 
    ( @order_start_dt datetime = null,
    @order_end_dt datetime = null,
    @season_str varchar(255) = null,
    @perf_start_dt datetime = null,
    @perf_end_dt datetime = null,
    @mos_str varchar(255) = null,
    @reprint_ind char(1) = 'N',
    @list_no int = null,
    @mailing_dt datetime = null,
    @mailing_type varchar(8) = null,
    @signer int = null,
    @label_ind char(1) = null,
    @include_general_public char(1) = 'N',
    @eaddress_type int = null,
    @eaddress_purpose varchar(8) = null,
    @eaddress_market_ind_no char(1) = null,
    @report_type char(1) = 'A', -- 'A' for ack, 'C' for confirmation, 'O' for single order, 'B' for billing
    @p_order_no int = null,
    @habo_flag int = null, -- 1 = yes, 2 = no, 3 = all; only used for confirmations
    @exception_flag int = null, -- 1 = yes, 2 = no, 3 = all; only used for confirmations
    @ob_no int = 0,
    @balance_type int = 4 -- default is all orders; 1=no payment, 2=fully paid, 3=partially paid, 5=any balance due
    )

    Hope this helps!

    Martin 

Children
No Data