• Votes

    5

    Workflows on a function should be easier

    The use of workflows in an object creation should be easier - for example sending something in the middle or completion of an automatic shipment. It should also be used ...
  • Votes

    9

    Ability to batch and send all posted invoices at the end of the day

    This might be possible with EDD, but it would be nice to make it easier to batch and send the day's posted sales invoices.
  • Votes

    3

    Imports needs to accept stanard XML layouts

    The import templates do not recognize all standard XML formats. Only a very plain one.
  • Votes

    8

    Zip codes populated need more than the east coast

    The zip codes table is not a complete list on initial install.
  • Votes

    1

    Flag changes on field controls

    Need an activity code to flag changes to field controls on a screen.
  • Votes

    2

    Activity Codes - Add a place for notes

    Add a comments field to the activity code function so that the information can be used to mark changes and log updates
  • Votes

    5

    Reporting support issues is too hard

    Let the customers decide which products they see on the portal. Let customers submit error messages directly from X3
  • Votes

    8

    Make it easier to see what NA add-ons are licensed

    Make a license reading for the NA key like you have for the normal license file. There used to be one on the NA Utilities menu, but it isn't there. Some can use F7 to ...
  • Votes

    4

    Bring back the EDI Monitor

    The EDI monitor allowed you to see files that were being imported, and it was used for more than just EDI - but other import templates as well.
  • Votes

    5

    Improve Import/Exporting automatically ftp files

    Add the ability to send a file to an ftp address. This would be an improvement instead of having to script the move from the local network directory where a script moves ...
  • Votes

    1

    Improve Import/Exporting allowing multiple tables on one line

    You can use *n fields to add special code, but this requires programming to have more than one table updated on a line. This should be easier to do.
  • Votes

    9

    Patching - need the ability to recover

    Patching should allow the ability to "undo" or recover from failed patches.
  • Planned

    32

    Patching is too complicated

    The Patching process takes too many steps. The messages are confusing, the patches should be cumulative.
  • Votes

    3

    Selection Screens should use the formulas

    The Shipment Selection screen has a place to enter a formula for selection. It would be useful to have that same ability in all screens.
  • Votes

    1

    Reports - Utilize Parameters

    Include the ability to use more parameters on reports to determine where they provide information, like inquiries
  • Votes

    9

    Reports - More "finished" customer facing reports

    The out of the box reports are not acceptable to use. The PO has addresses in the middle, which should be at the top. The format of the postal code should obey the ...
  • Votes

    5

    Patching is unexpedantly changing old functionality and creating ...

    The patches remove or break existing functions. It is hard to tell what is changing, and sometimes new versions are making old systems incompatible.
  • Votes

    2

    Platform Availability

    Post available platforms list on public site like Sage City so there is visibility into the plan.
  • Votes

    5

    Keep up with platform compatability - Windows 2012

    The lifecycles are too long between versions and there is not enough visibility into when the next SQL Server or in this case, Windows Server will be supported.
  • Votes

    2

    Improve interface tools for Java Bridge

    The tools for the Java Bridge are hard to use and the documentation doesn't explain it in enough detail