WDCi Blogs

In one of our recent projects, we are dealing with Quotes and Opportunities in Salesforce. We find that the Quote feature useful when it comes to creating quotation and opportunity data sync.

Within an opportunity, you can create multiple quotes which consist of quote details and quote line items. You can also save the quote as a PDF and send it to the customer. Let’s say if the customer has agreed to the quote, you can then sync the quote line items to update the opportunity line items. After the initial sync, updates to the quote line items and opportunity products will automatically be synced in bidirectional.

However, custom field sync between Quote and Opportunity is not supported out-of-box. You can see the feature request here:

http://success.salesforce.com/ideaview?id=08730000000HpBHAA0

Let’s hope that Salesforce will enhance this feature soon. Meanwhile, we just have to use a workaround to achieve this.

We are building an interesting integration between Salesforce and JobReady RTO. It synchronises course and student data between two systems. Stay tuned for more updates.

There is a feature in Boomi called ‘Trading Partner’ which can provide a solution for EDI integration.

The Trading Partner functionality can be configured with the details for both your company and your trading partners in terms of document standards and communication types.

For more details or information about Trading Partner configuration in Boomi, you can check out the documentation.

TIM would like to proudly announce that WDCi just turned 3 years old. Happy Birthday WDCi and have a great year ahead!

TIM has found a interesting article about Dell Boomi and WDCi.

Here is the link to the article: http://www.businesscloud9.com/content/dell-missing-link-enterprise-saas/5929

When integrating QuickBooks data to another application, syncing the accurate and relevant transaction information over to the destination application is very useful.

The easiest and simple way is to sync the specific transaction and its details. However, have ever you wonder if you want to get the other transaction details that are related to this transaction? And how can you get these details synced over whenever you create a transaction?

Lets have an example to explain the above situation.

• An accountant has just created a Sales Order in QuickBooks.
• Then, she converted this Sales Order into an Invoice.
• After that, she wants to sync this Invoice to another application
• So, this Invoice is being synced to the destination but the user wants to get more information about this Invoice, for example:

- Is the Invoice converted from Sales Order?

- Does this Invoice have any related invoice from the same Sales Order?

All these can be done with some tweaks in an integration process. Basically, what you have to do is to set the parameters when doing a request call for Invoice.

Here are the parameters that can be enabled to display/filter out the elements of the Invoice:

Lets say we have an Invoice that is converted from a Sales Order, so when we query out this Invoice,  we would like to know which Sales Order that this Invoice is converted from. We can set the parameter above (selected with red colour box), ‘IncludeLinkedTxns’ = true.

As we can see here, this is part of the Invoice response XML which we can get the Sales Order useful information from the Invoice.

Applications such as Quickbooks or Saasu have a mechanism to prevent cocurrent edit. If you plan to integrate with Quickbooks or integrate with Saasu, this is the mandatory field when you are performing an update call:

• Quickbooks uses a field called EditSequence 
• Saasu uses a field called LastUpdatedUid

This field value is automatically updated by the application after an update event. If two connections come in with the same value, one will succeed and one will fail.

This type of mechanism is also useful to prevent concurrent updates from a UI perspective. This is how it works:

• PersonA is editing a customer named WDCi. (current EditSequence=1000)
• PersonB is also editing a customer named WDCi using different machine (current EditSequence=1000)
• PersonA completes the modification first and click the save button. The request is then submitted to the server with EditSequence=1000. Now the new EditSequence = 1001
• PersonB completes the modication later and click the save button. The request is then submitted to the server with EditSequence=1000 but the server rejected the request because it does not match the latest EditSequence number (1001)

An Item in Dynamics GreatPlains can have one or more different types of ‘Price Level’. One of the complicated types of Price Level is the Price Method. This componet is crucial if you are integrating Dynamics GreatPlains with other applications:

So what does this Price Method define for an item’s price? Basically, it has can define how a price of an item is caculated.

Here we have a table showing the types of price method and their price caculation formula:

If you are integrating with Microsoft Dynamics GreatPlains, this is the high level data model for the finance module:

• A customer object is like a company. It doesn’t have an independent contact object.
• A customer can have many addresses. Inside each address, you can keep track of contact name.
• A customer can have many sales entries (Invoice and Sales Order).
• Each sales entry contains many sales lines. Each sales line is referring to an item.

Let us know if you are interested to know more!

In Magento, one SKU can have different product names. For example: If you have two different store views, you can have your product name in two different languages

• English: Table
• Spanish: Silla

To do this via the Magento Core API, you will need to:

1. Create the product using the catalogProductCreate function (default values)
2. Update the product in each store view using catalogProductUpdate function