My Products
Help
Florian Haase
PARTNER

Problem printing ShipmentConfirmation

by Florian Haase

Hi,

 

there is some bug in the API regarding printing of shipment confirmations:

 

In the userinterface, when we print a confirmation:

Skjermbilde1.PNG

 

Then we get this printout:

skjermbilde2.PNG

 

In the API when we do the same operation:

skjermbilde3.PNG

 

Then we get this printout:

skjermbilde4.PNG

 

The problem is maybe here:

skjermbilde5.PNGThere exists a special version for the Visma printout which overrides standard acumatica.

This is connected to the customer here:

skjermbilde6.PNG

 

The user interface takes the correct version of the printout but the API takes standard acumatica.

This is working on correctly on the SalesOrders.

 

Can you confirm?

 

Regards

 

Florian

4 REPLIES 4

by Yıldırım (Updated ‎30-10-2020 15:54 by Yıldırım VISMA )

Hello, 

We confirm the issue,  wrong report version chosen by Print Action via Shipment API. 

Once the following configuration correctly set in the UI,
1)Customer / Mailing Settings / Shipment Confirmation Report : SO.64.20.0S
2)Sales Order Preferences / Reporting Settings: SO.64.20.00
Customer_Shipment_report_S.png

Sales_order_pref_Base_shipment_report.png

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

ShipmentConfirmation report should be automatically picked by the system based on Customer's Document Language with the correct format as what UI returns. 

We've escalated this to the development team. 

Florian Haase
PARTNER

by Florian Haase

Thank you!

by Yıldırım

Hello Florian, 
the case has been confirmed as a bug. We'll continue to keep you informed of further developments when we receive more information.

Accepted solution
Yıldırım
VISMA

by Yıldırım (Updated ‎18-11-2020 08:48 by Yıldırım VISMA )

Hello, 

the case has been resolved and the development phase is completed. Unfortunately release date hasn't emerged at this moment. We'll be informing you about the release plan as more information becomes available.

Update:
This has been fixed in 8.27 Release