Agile Developer

Issue with PktDate ...
 
Notifications
Clear all

Issue with PktDate Logic in Axpert 11.3

1 Posts
1 Users
0 Reactions
232 Views
Posts: 609
Topic starter
(@banupriya)
Noble Member
Joined: 2 years ago

In Axpert Desktop, when we define 'AxpMaxSiteNo' and set its value to 99, the last four digits in the PktDate column of the SendPkts table will appear as 0102 (where 01 represents the from site and 02 the to site). If we set 'AxpMaxSiteNo' to 999, the last four digits will be 001002 (where 001 is from site and 002 is to site).

Currently, this functionality is not working in Axpert 11.3 or earlier versions. Please address this issue to align with the Axpert Desktop logic and provide us with a fix. In the example below, the transaction that generated the first row was saved from Axpert Desktop, while the second row was created from Axpert Web. Additionally, please verify the logic for the record ID between the Desktop and Web versions.

Note: This has been tested in Axpert Web 11.3, release 13.


Share: