Save Myriad Ordered with airSlate SignNow

Save myriad ordered

[Music] hi and welcome to squeeze become the connected marketplace today I'll be showing the latest and greatest changes we've made to the squeeze comm connect the software in the 1.14 release squeeze at the calm connector is a free piece of software developed by us that allows a business to connect any of its business software databases spreadsheets or files storing data into the squeeze the common toad X platforms allowing businesses to save and make more money by automating data management and transfer between its systems and other supplier and customer systems now you understand what the connector can do let's look at the changes we've made to the connector in the 1.14 release this release adds improvements the does that feature to allow categories to be assigned to category tree IDs this allows data for multiple category trees to be managed and exported from a dataset by setting up multiple category trees it allows businesses to provide multiple ways for users to navigate through categories to find products they are looking for which the 1.10 connector release video if you are unsure what data sets are and links to it can be found in this youtube's long description additionally we've added new fields to sales orders imported into the connector to be able to set external location data against the orders this allows third-party location information such as nominated dealers on sellers suppliers or pickup points to be specified in an order which is very handy to note when a customer has designated for ordered products to be picked up from a certain location or that a separate organization should receive a fee for an order next we've increased the time outs when data exports run to push data interconnected ecommerce platforms this helps when the connector has to push large amounts of records or is exporting data across slower internet connections the extent of timeouts reduce the chance of exports failing ensuring that the data gets pushed across lastly we've made improvements to the micro net distribution adapted within the connector when an exports account product pricing data from the micro net system to be out a group contract based pricing helping it to reduce the amount of pricing records that need to be exported now before I get started and showing the latest improvements feel free to subscribe to the squeezed dot-com youtube channel to stay informed when we release new great functionality in the future in the 1.14 connector release we've added a new field to be able to set a unique identifier against category records today a category tree that category can be assigned to so within the connector able to click on the datasets tab I already have an existing data set that has been created here if we do and open that data set this data set already has a list aprox that has been imported or set up within it now if we go into the categories tab within the category sub tab the new column that we've added to the data set is called key category tree ID and this is where we can specify a category tree that categories are assigned to so in our example here we have five different categories that we may wish to assign products to and these are the categories that users will navigate through on websites or connected ecommerce platforms in order to find the products that they are looking for so we have two categories here called bags and clothes and this denotes the kinds of products that could be related to these categories the other three categories we have here are based on brand so we have the Chanel brand the Gucci brand and the Camelback brand as well if users know the brand of the kind of products they are looking for then they could click on these categories than to view those associated products so what we want to do within the data set here is we want to sign one set of categories to one category tree and another set of categories to a separate category tree within the key category tree ID field we may need to put in a unique identifier of the category tree now the associated systems where this category tree data is being imported to will be able to provide you what the unique identifiers for those trees are those systems could allow you to provide or set a key category a tree there so if we take an example we could set the key category of the bags and clothes we could set them to an identify of one and for the brand based categories we could give that a category tree identifier of brands so we just assign that to each of these categories when all this data is exported out from the data set and imported into associate ecommerce platform those platforms can look at this column in order to work out which categories needs it could be assigned to which trees which in turn will determine where those categories appear and how users can navigate through to find the categories that they are looking for so if we were to create another category such as if we're selling camel bags we may also be selling abs backpacks we would assign that to the brands category tree also give that a code and it's as simple as that that category can now appear under the category tree within the finds drop-down we can also search for categories that are associated to a given category tree if we choose the key category tree ID filter that type in the value of the key category tree that we want to search for click the find button we can only see categories assigned to that brands category tree so this is a useful filter if somebody's managing setting up this category data they only want to work with categories that assigned to one tree at a time this is an easy way to do that once we're happy with our data we'd need to be also to be able to export this category tree ID column data if we go into any of the doctors there is now a key category tree add a field which we can export with category data so if we just go into our an example adaptor here this is generic adaptor click on the data exports option and click on the category export if we just assign that to a such as an ODBC or a compatible database you've seen the database fields that there is another field that is available now it's called the key category tree ID so if we're getting it out from a database we can specify the column name in the table that stores categories such as it could be called a category tree or ID in a different business system then we just need to specify that there and activate that field in order to then get that key category tree data coming out and if we look at other adapters so for example if you look at the micro node adapter in the categories data export you can see there is the key category tree ID field they're available so it's across any adapters that export out categories or category product records where this new field has been added and can be enabled to be set for the category data being exported out another improvement we add it to the connector is to do with sales orders and having additional fields available within sales orders so if we go to click on the sales orders tab and click on the order number of an existing sales order this opens up the sales order details where we can view all the details of the sales order that has been imported into the connector software if we click under the dispatch and freight tab we can see that there are now three additional fields that can have data set for us this is external location code external location name and external key location ID using each of these fields allows us to specify an external location that this sales order may be linked to and what I mean by an external location and a location external to the business where the sales order is being created against where this order could be delivered to picked up from or with fees or step ends other information needs to be linked back from one sales order to another company or another entity so if we take an example when this order is being created that the customer was able to specify a supplier where they wanted to pick up the ordered goods from an external location code we could have an ID of a supplier that is set up as a location within the Associated accounting of business systems so we could have supplier 0:01 that supplier could have a name it could be Lee's hardware store and that location could have a unique identifier such as zero zero one within our business or accounting system that that location is defined that by using this data we can now look at this ordering go the order has been assigned to Lee's hardware store which is an external location from our own business and we need to deliver goods to Lee's hardware store instead of delivering it directly to the end-users location from this data could potentially pay Lee's hardware store for managing the order or we could charge them in order to pay for the goods and then when the customer comes into their store then the customer will pay them these additional fields provide us with a lot of flexibility when we want to link separate organizations or entities to organizations entities locations to a sales order and then we can run reports as well as make business decisions on the data that is available within the order now to get this data into an Associated accounting or enterprise resource planning system there's a few options that we have made available to the connector so if we go back to the adapters and messages in any generic adapter we can use the generic adapter the import sales orders into any compatible databases data files or connected web services if we click on the data imports tab and we choose the sales orders import type and we sign that to our Associated data source in the data fields we're now seeing the list the three fields that have been added the external key location ID the external location code and external location name so we can now go off and wherever we're saving this data to we can provide the names of the columns in any our Associated business system and then we can do the same for that activate those fields and choose the kind of data that needs to be imported into the table where that data is stored if this was a database for example so this flexibility once again in here to be able to choose if we want to save this external location data against orders in the appropriate systems that's how we set it up for the generic adapter if we set up the my ab EXO adapter then click on the settings for the my ab EXO adapter within the adapter there's a setting here called sales order dispatch field format so what we can do is when a sales order is imported into the 'maybe EXO system when it saves data to the the dispatch field the external location data it will be placed into the dispatch field that is available in sales orders from that system and we've got hooks that are available here so they've got the curly brackets around the name and the external location code as well as the key external key location ID where we can specify what pieces of the data about the external location we want to put into the dispatch field so then that allows us to run reports and do other things in EXO in order to utilize the data coming in for the external location and in the future we can look at other adapters I don't know how to get this data into the Associated systems a small useful improvement we added to the connector is when we're exporting data for any adapters if we click on the export routines button this allows us to choose to run data exports where we can exports different types of data so if we want to export product data to an Associated ecommerce platform we just need to select that export and click the run once off or we can schedule it into run a particular date and time on an ongoing basis now the improvement we've added is that we increase the time out where the connector will wait for the data to be sent across to the Associated platform before the connector gives up now previously for data exports that that timeout period was set at a hundred and twenty seconds it was set at 100 seconds or a minute 40 but now we've increased that to 200 seconds which is three minutes twenty seconds to export the data out for most data exports that is not going to be a problem that's a very long time to import what is typically small amounts of data but for some specific exports we've increased the timeouts even further so the product pricing data exports typically there's a lot of pricing data digadz exported out there over ten minutes in size we've increased them export make model mappings timeout that is increased to 35 minutes because you can have lots of products assigned to lots of makes and models especially if you're working in certain industries and as well as the the exporting of the product account pricing data that is also a 35 minute timeouts these extended timeouts allow the connector to wait for longer for the data to be sent across the internet and imported into the Associated ecommerce platform and for that platform then to return a successful response now the timeouts are here to make sure that the connector is not waiting forever it's for these exports to complete because sometimes the internet connections can sever or the e-commerce platforms never return a response due to a myriad of reasons for that the last improvement we've added to the 1.14 connector release has to do with the micro net distribution adapter so this adapter allows us the export contract based pricing from the micro net distribution system for go into the micro net distribution system settings window and click on the data exporting tab a new setting that we've added to the adapter is this setting called group contract category discount pricing and an either has the options of yes or no and what this setting does is it says whether or not the adapter when I wanted to get out contract based pricing for specific customer counts known as debtors in micronet system when it exports that data out whether or not it's trying to group the pricing together to try to reduce the amount of pricing records that are exported out to show you an example of how this works in effect if we look at the micro net distribution system it has concept of being able to set up contract a contracts allow us to set prices for specific customers when they buy certain products a typical way that most accounting an earpiece work is where use first set price level prices you sign customers through these different price levels and maybe for a handful of customers you want to give them different pricing such as discounts or extra charges that are different from the price levels such as if you're doing deals with certain customers so within the micro net system here we can set up contracts and contracts we can say which customers these contracts apply to and as part of that we can say which products are assigned to the contracts one of the things that the micro net system can do if I discounts in contracts against certain categories so we look at an example here we've got a a rule that setup is that we're going to provide discounts on the price level pricing for a given category such as this 109 G one here so we've got different quantity breaks so we're going to discount by 92 percent when the customer orders 500 for all the products that are signed within this 109 G one category and we can set different discounts for different quantity breaks for all the products assigned to this one category now if we do this across a large set of products and in this example we can a discount against all the categories of products assigned to and when we do this that the adapter pulling out the pricing needs to get out the entire inventory list for all the products that are assigned to this contract and all the discount breaks if we sold many tens of thousands of products applied against the 16 different price levels of the micronet system supports we can get up in the tens of millions of pricing records that the adapter within the connector needs to generate and most ecommerce platforms very much struggle to be able to import tens of millions of pricing records in the adapter if we turn this setting on to yes then what the adapter will do is it will try to find if there are multiple contracts within the micro net system that have the same discounts applied against the same category it will bundle those prices together by doing so it will reduce the amount of pricing records that need to be exported out in our example week would have tens of contracts that allow for discounts across our entire inventory set and if we're selling tens of thousands of products this one change would reduce the price records from being exporting out tens or hundreds of millions prices down to only a couple of million prices the only time we want to turn this city to yes is if within the micro net distribution system we are setting up category discount break prices that allow discounting across many products in a category and that there are many contracts to have the same discounts for the same category now if we don't have that kind of situation set up in the micro net system then this setting it might as well be set to no because otherwise the adapter has to do more processing in order to do more calculations in order to do the grouping which takes longer for the adapter to do this kind of style where we using contracts to effectively discount across an entire inventory it may be a very unique case it's not typical of what most businesses do where they they usually use the price levels against products in order to manage that as opposed to contracts so this improvement depending on how the data is configured in the micro system could be the difference of the adapter having to export tens upon tens of millions of prices and it could be reducing it by a factor of 100 or it could make very little difference if there is more what we call entropy or there's more randomness in the the pricing data that is exported out and the adapter isn't able to group contract prices before turning this set on you need to have a look at the micro net system look at the way the contract data is set up and that will determine whether or not this setting should be left to no or should be turned on to yes that's a wrap up of the 1.14 connector release for more details you can also view the connector documentation that squeezed calm docks connector thanks for taking the time to listen until next time have fun with the connector you