Friday, January 23, 2015

Can SmartConnect Integrate Dynamics GP & Salesforce.com?

We've seen it before... just a typical day in the office for the Accounts Payable team until their worst fear from the Sales team enters the room and informs them that the biggest sale of all time had been lost due to lack of integration between Dynamics GP & Salesforce.com. Now the task of integrating the two rests on a lone member of the AP team... is this the end? Is all hope lost?

Luckily for him a super solution shows up to save the day! Find out how the situation plays out in this epic tale below:


For more information on SmartConnect & how it integrates with Salesforce.com click here or email our team at sales@eonesolutions.com! We'd love to set you up with this super solution!

Tuesday, January 20, 2015

Tech Tuesday: SmartConnect and CRM - Setting Picklists using Multi-Lookups

This week's Tech Tuesday is from our Senior Technical Consultant, Chris Hanson, who will walk you through a scenario with SmartConnect & Microsoft Dynamics CRM.

When working with CRM oftentimes you will need to set the value of one or more picklists. Normally, the data in the source doesn’t match what CRM wants for the picklist or option set. To map to a piclist you need to provide a numeric value.  

You can do this using calculated fields and translations if you have a set amount of possibilities, but if you are adding new values to the picklists often it makes it difficult – as you have to update your code every time you add in a new value.

We can use a multi-lookup to dynamically get the needed value without ever having to update it after it has been set. The multi-lookup will point to the String Map table/entity which stores all the picklist info for the entire CRM organization – which means we need some additional data to complete it:

 To use the multi-lookup to get the picklist from CRM you need to do the following:

1. You need to have the string value you are passing in (which you do, it’s the text value you have)

2. You need the technical name of the entity you are importing to, for this example Account is account. You need to find that through the customization window in CRM for that entity. 


3. You need the AttributeName of the picklist you are setting. You need to find that through the customization window in CRM for that entity for that specific field as well.

 
4. Once you have those, you can build the multi-lookup you need. The objecttypecode/entityname and AttributeName values should be hardcoded in the source data as those won’t ever change.




5. Then your lookup will look like the following:



- The entity selected at the top should always be stringmap. It is your choice on whether to return an error or not if it doesn’t find a value.

- The objecttypecode and attributename fields should be compared against the values you hardcoded in your source data when you aliased them in.

- The value field should be compared against your field that has the text value in it

- The return field should be the attributevalue as that is what holds the numeric value you need to map to the picklist



6. When you save this multi-lookup you can then map it directly to the industry field that you need in the mapping.





7. This process can be used for any others that will have the picklist values changing as long as you switch the values for the objectype and attributename fields. If you do multiples in the same mapping you’ll just have to change the aliased field names to ObjectType2 AttributeName2 etc for each additional set.

Interested in learning more about SmartConnect and CRM? Feel free to email us at sales@eonesolutions.com and we'd be happy to help!

 

Friday, January 16, 2015

Five Words To Ruin A Date

Throughout the years we have been steadily increasing our activity on the popular social media platform, Twitter. We always enjoy a fun interaction amidst the informative tweets and ramblings of those we follow. This week we had a wonderful interaction with Frank Heslin, a Financial Systems Administrator of ExamWorks, Inc., and his humorous take on the hashtag #FiveWordsToRuinADate:


To which we responded: 

 

So please, take our advice and be sure to never utter these two phrases to anyone in the Microsoft Dynamics GP world. :)

Happy Friday!

Thursday, January 15, 2015

New Support Options at eOne!

We're pleased to announce that we have have made support simpler than ever by offering support by the hour and annual support packs per product for our customers! Please note that all our old support options have been replaced with the following:

eOne Professional Services 1 Hour - $215/hour (2 hour minimum)
If you only need help to get through the next hurdle - then a simple 1 hour support block is your way to go. You can purchase support at the rate of $215/hour and add on the time you need. (Note that with you initial purchase you are required to purchase 2 hours up front but then can add on time in 1 hour blocks. All hours expire two calendar years from purchase date.)

Product Base Annual Support
The support packs are available for purchase per product, per customer giving you access for 1 year from the purchase date to our support team via email or phone. This is a great solutions for customers who have multiple users on the product and have utilized our team for multiple questions on the past. (Please note that annual support is an additional purchase to the product and required annual maintenance. Training and services are not included as part of the annual support pack.) Please see support pack prices below:

SmartList Builder: $1000/year/customer
SmartConnect: $1950/year/customer
Extender: $1000/year/customer
SmartView: $500/year/customer
Node Builder: $500/year/customer
SmartPost: $300/year/customer
 Flexicoder: $500/year/customer

Interested in purchasing right away? Check out our shop page here and get started!

We have been busy working on a lot of new changes at eOne - be sure to subscribe to our blog (add email in the right column) so that you are always up to date with our team!

Tuesday, January 13, 2015

Tech Tuesday: Creating Document Distributions with SmartConnect


This week's Tech Tuesday is from our Support Guru, Pat Roth, with his descriptive article on SmartConnect and Receivable Transactions!

There are a few common issues I’ve seen with document distributions when creating them using SmartConnect. This is blog talks about Receivables Transactions, but it would apply to pretty much any kind of Dynamics GP destination and mapping.

The first one is:

I’m creating a Receivables Transaction Invoice document and providing the distributions. The document is created successfully however the distributions are created unbalanced or duplicated. What is wrong in SmartConnect?


                                                                                   Figure 1: Unbalanced distribution after integration

In the figure above, we can see there are 3 SALES distributions and one RECV – the distributions are out of balance and so the document would not post. Looking more carefully at the distributions, the first two ($20 and $30) are the distributions that I integrated in my source data.

This observation is correct – the first two distributions are the ones that came from the source data. The last two have been created by eConnect automatically as we failed to tell eConnect (via SmartConnect) to not create them.

In the SmartConnect map on the ‘Create transaction’ node, make sure the column “autocreate distributions” is set to 0.

By default, eConnect will assume that it should create the distributions and not mapping the column would let eConnect default this parameter and create the distributions. So by mapping our distributions and leaving this field empty – we get double the intended distributions.


                                                                Figure 2: Set Auto-create distributions to 0 (zero)

That leads to problem two:


I disabled the eConnect auto-create of distributions. Now I find that SmartConnect didn’t create the distributions properly and now the document has unbalanced distributions.

 Figure 3: Integration with auto-create distributions disabled

This is a misinterpretation of how eConnect creates the distributions.

eConnect will either create all distributions or none of the distributions. There isn’t a way for it to be set to “create the distributions that are not provided”.

In this case, a common issue we see is that the user source data does not contain all of the distributions necessary to create a balanced transaction. Typically only the SALES (or PURCH on the PM side) distributions are provided and not the offset accounts.



Figure 4: Representative data only containing the SALES distribution amounts  

For the example above, the document AD1001 has been successfully created and the two SALES distributions for $20 and $30 are created successfully – but we are missing the offset RECV distribution for $50.

This is a problem because while we can use grouping in SmartConnect to take two (or more) lines and group them into one line, there isn’t really a way to create new lines. Nor can we map multiple data sources (somehow) into an already mapped node such as this ‘add distribution’ node.

Fortunately we don’t have to – we can do it with SmartConnect 2014 and above (sorry, it does not work in previous versions).

In order to create more distributions, we need to be able to map more distribution lines. In order to do that, we need another entity to map to that will create distributions. Once we have that, we can then summarize our existing data to that mapped line to create the offset distribution.

In the Microsoft Dynamics GP Node Maintenance window, find the Receivables node and expand it to find the Receivables Transactions node.

Right Click on the “Receivables Transactions” node and choose Add Existing Node


Figure 5: Add Existing Node

Select the taRMDistribution (for this example):


 Figure 6: Adding taRMDistribution  

Once that processes, SmartConnect will add the new node with the default name to the list of nodes.

Figure 7: New 'Add distribution' node added

Right click on the new ‘Add distribution’ node and choose ‘Edit Node’


 Figure 8: Change the name from the default "Add distribution"

Once the Display Name has been changed, we don’t need or want to change anything else. Just press Save.


Figure 9: Distribution Renamed

We can see that the UI now shows the new node with the new name.

In this case, I named it ‘Add RECV distribution’ since that was what I plan on using it for. But that is just the name – I can use the node the exact same way as the built-in ‘Add distribution’ node that already exists.

The last thing we need to do is move the node position. Currently the new node is last in the sequence and we should really put it around the same spot as the existing node.

To do this, select the new ‘Add RECV distribution’ node, choose “Move” and then “Up”.

Keep doing this until it is above or below the existing ‘Add distribution’ node.

My final result is:


Figure 10: Final change

Lastly, press the Save button on the Node Maintenance window to save our hard work.

Opening our existing map, we see that it now shows the new ‘Add RECV distribution’ node.


                                                                                           Figure 11: Map with new node

In this case, from our data we see the intent is that the document would be grouped by the Customer & the Document Number. We would deduce then that while there isn’t a column for “Document Amount”, it must be the SUM() of the DistAmount column.



 Figure 12: Source data mapping

Normally we wouldn’t group the distribution data – but in this case we do because we need to SUM the distribution amounts in order to get our offset distribution.

Here, we are hard coding the offset RECV account to the Fabrikam default account of 000-1200-00.

The Distribution type is hard coded to 3 (RECV) for this distribution to be created.

The DistAmount column is set to SUM and mapped to the DebitAmount column. The rest are self-explanatory.

Looking at the resulting document created in Dynamics GP, the distributions are now balanced and what we would expect to see.


Figure 13: Correct document distributions after integration

Until next time,

Patrick
eOne


Interested in learning more about SmartConnect? Email us at sales@eonesolutions.com for more info!