Does anyone here actually work at SAGE?

SUGGESTED

Is there any sage employees on this forum, if so, please speak up.  Where do we report bugs?

Parents
  • 0
    SUGGESTED

    Hi ,

    Thanks for reaching out. Ideas and suggestions to help improve Sage BusinessVision's business usefulness and to help improve efficiency can be posted and or voted on here. The R&D team uses top suggestions to determine their yearly work-plan. 

    Hope this helps, 
    Warm Regards, 
    Erzsi

  • 0 in reply to Erzsi_I

    This issue involves an order "PO Number" being truncated when importing or exporting to/from BV.
    BV expects a file called "Order.txt" for importing orders. It will also export orders using this filename as the output document.
    Within that file each order consists of multiple lines.
    The first line for an order is the header line.
    It's the "PO Number" field which is being truncated and I believe this to be a bug.
    The "Customer PO Number" field, I'm using as a relative reference because they're both PO Numbers and they have the same datatype and character length limits in the pervasive sql database.
    Both have a length limit of 20 chars.

    I'm using the same data for both of these fields, formatted like so.
    "MagOrdNo:0000000001" (19 chars)

    On import, this data saves properly to the "Customer PO Number" field within the database and it also displays properly in the BV GUI for the order.

    However, the "PO Number" field saves the data to the database/(and displays on the GUI) as: " /MagOrderN"
    NOTE: the prefix of 10 SPACES followed by "/" followed by 10 chars of the provided data.

    The "PO Number" field data is displayed on the Order GUI in the "RefNo:" field.

    Why do i think this is a bug?

    If you create an order using the GUI and type "MagOrdNo:0000000001" into the "RefNo:" field, it will properly save it to the order and database as expected. It will not truncate it and prepend spaces and a slash.

    If you export that order from BV to Order.txt, it will truncate it. The purpose of the Order export is to be able to move all existing orders to a new system running BV. If you did that using this order number (once again, which bv lets you enter in the gui), it would not export properly. So that order would not import properly into a new system.

  • 0 in reply to slacka

    Also, it appears this issue was pointed out over 10 years ago in this post. Which is why i asked if anyone from sage is even here reading these posts. https://www.sagecity.com/ca/sage_businessvision/f/sage-businessvision-forum/27479/order-file-import---comment-records

  • 0 in reply to slacka

    wow that's unfortunate.. doesn't make me feel very confident about getting an answer to my question :( is there no "Export Data" feature in the old version of BV DELTA 6.22?

  • 0 in reply to tco

    I can't answer your specific question but I was able to get in contact with someone via chat.  Couldn't reproduce the export bug, but the import bug was found and submitted to their dev team (at least i hope that happened).  There may be hope for you. 

Reply
  • 0 in reply to tco

    I can't answer your specific question but I was able to get in contact with someone via chat.  Couldn't reproduce the export bug, but the import bug was found and submitted to their dev team (at least i hope that happened).  There may be hope for you. 

Children
No Data