Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
  • UTF-8 is supported
  • Sales Orders created in SupplyStream will not generate a Push Dispatch Confirmation message unless specifically requested.
  • If you use any leading zeroes in the data you provide, then this needs to be in quotes. For example, "SalesOrderNumber": "000000011".
  • Specifying a " in the text of a JSON file will cause an error.
  • For Push CSV messages, if the file contains the delimiter in the text, the text will automatically be put into quotation marks (").
  • All HUB push messages use UTC - Coordinated Universal Time.
  • Fields that reference 'placeholder': a field has been created within the message and maybe also the database with future use/functionality in mind.

...

  • The Push scheduler runs every approx. 15 minutes.
  • The iHub shows the first error that in finds on an upload. Once you fix this error and re-attempt the upload, it may fail again for another reason.

  • No address validation within the Hub. 
  • Files from different DC's are not combined. For example, two Push Stock Overnight Summaries generated by different DC's within the same time zone would send as two separate messages/files. 

Supported iHub date formats

CSV: Any format can be mapped. Must be defined during the CSV mapping process.

Other (i.e. API):  yyyy-MM-dd, yyyy-MM-ddT00:00:00.001Z


Push mapping (API and FTP)

During integration push API and FTP mapping, features include:

  • Adding placeholder fields with a static value
  • Renaming fields
  • Reordering fields
  • Ignoring fields
  • Change field type