Thursday, April 17, 2014

eOne's 2014 Goals & Successes

Everyone works really hard and sometimes we set goals and strive to hit those goals. Often when we hit those goals and are successful as a group – we turn around the next day and start on the next goal.  I think it is important for small businesses like ours to celebrate their successes. 

Over the past few months eOne has set and reached some goals and I would like to highlight them here. 

1.     Goal to reach 2000 SmartConnect Customers: For some time we have been aiming at reaching the 2000 customer target for SmartConnect. For a product that has existed for only 5 years - It is a great achievement, which we were really excited about, to reach the 2000 customer number in March 2014.  This means that there are 2000 mid-market companies that rely every day on SmartConnect to help run their business. That is a humbling responsibility. 

A massive congratulations goes to our development team Kevin, Ruaan and Sarvanaz for continuing to produce such a high quality product. I also need to highlight Dave, Chris D, Chris H and Lorren who provide all the support and implementation skills that let us sell. And last but certainly not least thanks to Abbey who has made these sales happen.

2.     Goal to sell 80% as much SmartList Builder as Microsoft did:  This goal was something we thought would be a steep one. The great result is that in the first quarter of 2014 we sold MORE SmartList Builders than Microsoft had sold in the same quarter a year before. This is a direct results of having great resellers. The direct responsibility goes to our sales and sales support team on getting the message out there effectively. A huge thanks to Abbey, Danielle, Alicia and Lauri.

3.     Goal to provide our resellers the easiest possible way to make AEP payments and keep track of the eOne modules their customers own: I measure this as a raging success for a few reasons – the first being that since Jan 1st we have processed 3319 module renewals almost seamlessly. There are always a few hiccups but overall it has been a great experience.

I add to this feedback from our resellers that goes like this: “This is the easiest site we work with and we work with 50 different ISV’s” and “Thank you for making such a great site, paying everything online without having to talk to anyone means I save so much time”.

So a huge thanks to Lauri, Bob, Jason, Alicia and SmartConnect for helping us get the new fully integrated processes running on the website.

I was back visiting our Australian office in March when we hit the 2000 SmartConnect customer  - so took the dev team out for a celebratory lunch – that started at 12pm and ended up sometime around 4pm.  It was a good thing that the only way home was public transport! 

We are shortly to have a celebration in our Fargo office – just waiting for the weather to warm up a little!

Tuesday, April 15, 2014

Tech Tuesday: SmartConnect Processing Sequence

Our Director of Professional Services, Lorren Zemke, will be taking you through the SmartConnect processing sequence for this week's Tech Tuesday!

In this article I am continuing my series of discussions on how SmartConnect processes data. Previously I've used examples on summing values and working with line sequence numbers. Today I will diagram the process flow of SmartConnect, using the process of sending data to Microsoft Dynamics GP but the same process is used for all maps.

The basic steps fall into the following categories:
  1. Pre-Map Tasks
  2. Data Read
  3. Transformation
  4. Pre-Document Tasks
  5. Document Send
  6. Post Document Tasks
  7. Post Map Tasks

Pre-Map Tasks 

Pre-Map tasks are executed before the data is read from the data source. This can be document processing tasks such as moving files, running scripts to ask the user for values, running another map and reading data from a SQL table. 


Data Read 

Pre-map tasks have finished executing and the data is being read from the data source. 

One specific task within SmartConnect, after the data is read, is called SQL Validation. This task is used to query SQL tables based on data from the data source. The Validation logic can verify if data exists or does not exist allowing the map to stop processing if the logic is not met. 

This section of data is processed before it is sent to the destination. All of the column calculations are done at this time and the data is prepped for sending to the destination. In the case of Dynamics GP, SmartConnect is creating the XML file that will eventually be sent to eConnect. In a call to a web service destination, SmartConnect is generating the object needed to make the call and send data to that web service.

Pre-Document Tasks

The tasks created in this section happen immediately before each document is sent to its destination. At this point all data has been retrieved and all calculations with the map have taken place.
Use the tasks in this section for setting global variable data that will need to be used for Post Document or Post Map tasks.

If you are using Global Variables in your map, you can clear them out at this time to get them ready for the next document unless you need them for a Post Document or Post Map Task.

Document Send
SmartConnect creates a connection to the destination and sends a single document.

Post Document Tasks
Once a document has been sent to the destination, based on whether the document was successful will determine which set of Post Document Tasks will execute. Tasks can run if the document was successfully integrated or not. If a task needs to run regardless of whether the document was successful or not, the task needs to be placed.

The Pre-Document Tasks, Document Send and Post Document Tasks will continue to loop based on the value set for the Map Keys on the Data Source section of the map.

Post Map Tasks
After all data has been sent to the destination, SmartConnect determines if the map was successful or not to determine which set of tasks to execute. For all destinations but Dynamics GP it will depend if even one document or task is listed as having failed, the tasks that are part of the failed document section will execute. Only if 100% of the documents are successful will the map success tasks execute.

Happy Integrating!

Interested in learning more about SmartConnect? Reach out to our Sales Team at for more information!

Thursday, April 10, 2014

How to Create Quotes/Invoices on the eOne Website

Lately we have been creating multiple how-to website videos that highlight the basic and most important features of our website. The following video will show you how to create quotes/invoices directly on our site making it easier and more efficient for you to quote our products and services!

If you have any questions or additional feature requests regarding our website please feel free to let us know by emailing:

Tuesday, April 08, 2014

Tech Tuesday: Using a Go To that Populates a Microsoft Dynamics GP Combo Box

This week's Tech Tuesday is by our Quality Assurance guru, Jared Dux, who gives a great example of how to set up a Go To properly on the Account Summary SmartList in SmartList Builder.

Sometimes when setting up a Go To in SmartList Builder the value trying to be passed is not populated in the Microsoft Dynamics GP window being targeted. This usually happens when the wrong data is used. A good example of this is the Detail Inquiry window in Microsoft Dynamics GP. The year field is required, but the combo box expects a string rather than an actual date, so selecting a date field in your Go To setup will not function properly. The example below will describe how to set up the Go To properly on the Account Summary SmartList.

Set up a calculated field to make the Year a string

  1. Enter Year_Calc as the Field Name 
  2. Set the field type to String
  3. Add the year field as the Calculation like: {Account Summary:Year} 
  4. Save the calculated field

Set up the Go To

  1. Add a new Open Form Go To
  2. Name your Go To, select Microsoft Dynamics GP as the Product, select Financial as the Series, and select Detail Inquiry as the Form.
  3. Add a task to populate the Account Number
    • Select Set a field value and run the field script for the Task Type
    • Select Account Number as the Field
    • Select Account Summary as the Table
    • Select Account Number as the Value and save the task
  4. Add an additional task to populate the date with the calculated field
    • Select Set the value of a field for the Task Type
    • Select Current Year CMB as the Field
    • Select Calculated Fields as the table
    • Select Year_Calc as the Value and save the task

When the Go To is used now, the year will be populated in the target window and the correct data will be returned.

Curious to learn more about SmartList Builder? Email to learn more!