Page tree
Skip to end of metadata
Go to start of metadata

Linking Parsers to Customers is necessary so that you can use the More → Upload File to import the file, or via Email Import


Table of Contents


Connecting the Parser to the Customer

In the Search Anything box type Parsers to find the Parsers menu. Within this menu there are the available Parsers listed - these can be added to. Contact our support team to have new parsers created, or refer to our guide: Making your own Parsers



Use the View Link to view the Parser and see the current settings as well as which customers its enabled as an option for. Use the Add Customer to Parser link to add more customers to use that Parser, or delete customers if the link between customer and parser is no longer required.



Then using the edit buttons you are able to change the To Address - which is where your customer needs to send files to be read automatically by the parser. Editing the parser settings further than this usually requires a higher level of knowledge as it may cause the Parser to not function if they are changed without changing the underlying system controlling how the parser works.


Connecting the Customers Email Addresses to the Parser

The next step is to connect the parser to the customers email addresses.

From the Edit Customers page (Contacts → Customers → Edit), head to the Email tab.

At the moment only the email address: "admin@burleighpies.com.au" is added, so we need to create a new email address for john@burleighpies.com.au.
Enter his email address into the New email section and then click Add new email

On the following page, enter the persons name (optional), then add them to the Parser. From here you can also enable various email Notifications. In this example we clicked "Manifest Notification".

Then click Save.


Never link two parsers to a single email address which have the same To Address.

This will cause problems because upon import the system will not know which parser to use and will just go with whichever Parser it finds first. This leads to unpredictability in how the data is parsed.



Wildcard Email Addresses (*@domain.com)

Wilcard email addresses allow you to configure anything at a particular domian to work with a given parser.

For example, anything@burleighpies.com.au → sale_orders+bruce_transport@in.cartoncloud.com.au can be setup by a single email address.

Wildcard email addresses are added by using a * character before the @ symbol. For example:

*@burleighpies.com.au

With this added, we no longer need the john@burleighpies.com.au email address in order for the parser to work, we can actually delete that out. The only reason to keep it in there is if we wanted to allow John to receive certain Notifications.

For this example, we don't, so we'll delete him:

And we're done. Now, anyone emailing from an @burleighpies.com.au email address will be able to send Sale Orders to: sale_orders+bruce_transport@in.cartoncloud.com.au



Parser To/From Details to send to Customers

You can find the parser information for your customers to start using their parsers here:


In the Contacts drop down menu → Customers       

                                                                                      


Search for a Customer →

                                                                           


Select the "Edit" function →


                                                                                                              


Go to "Parser" tab and here you can see the details that you need to send to your customer:

  • Accepted Filetypes
  • Allowed From Address(es)
  • To Address


                    


Understanding To Email Address Formats within Parsers:

Typically, email addresses for parsers are in the format:

{type}+{slug}@in.cartoncloud.com.au

ie: sale_orders+bruce_transport@in.cartoncloud.com.au


type:

This is the type of email being loaded in. The type can actually be anything, however we generally make it clear as to what the parser is designed to import because this helps when you have multiple parsers, for example:

sale_orders+bruce_transport@in.cartoncloud.com.au
purchase_orders+bruce_transport@in.cartoncloud.com.au
manifests+bruce_transport@in.cartoncloud.com.au
invoices+bruce_transport@in.cartoncloud.com.au

For this reason, using a type such as "orders" would be a poor choice because then when you have clients sending you both Sale Orders and Purchase Orders it is not obvious which email address to send to.

slug:

The slug is the name of the tenant as specified in the URL at the top of the page. Email addresses are case-insensitive so you can use whatever case you want in the email address.

In this example, the slug in the URL is Bruce_Transport. Therefore, the slug in the email address can be bruce_transport, Bruce_Transport, BRUCE_TRANSPORT or any other case-variation.



  • No labels