|
Field Mappings
Each integration will come
with some default mappings setup for you. But, you can customize
the system to fit your needs by setting up mappings that
are:
- One-to-one - Where the destination field
is pulled directly from a source field
- Constant value - When every integrated
object will have the same value for a specific field (like
the "Customer Source" field always being "GP").
- C# Scripting - Add C# scripting on any
field mapping to do complicated
data manipulation.
|

Figure 1.3 - Field Mappings
|
|
Customize
But this is just
the beginning! While the Bridge will come "out-of-the-box" with
all the integrations on with some default mappings, you
can customize the system endlessly by:
- Adding Filters - Add filters on any
integration to prevent all data from being integrated.
This is useful if you have Accounts in Microsoft CRM
that you don't necessarily want in to Microsoft Dynamics
GP.
- Add Schedules - Setting up schedules
for integrations to specify when that integration should
occur. If you do mass updates at night on your products
you don't want this integration to interfere with order
processing in the morning. Setup the integration to run
as a 'background' integration and other integrations
take precedence.
- Add Custom Field Mappings - Microsoft
CRM allows you to add new fields onto the object
schemas. As soon as the schema is published you can map
those fields in the Bridge. By adding fields onto your
schemas, you can show any Microsoft Dynamics GP
information you'd like to see in Microsoft CRM!
Cut out the need for people to keep asking for information.
Order Integration
The Integration
Bridge also supports a full order integration loop,
meaning your Microsoft CRM users will know the status
of an order in Microsoft Dynamics GP at all
times.
|
Figure 1.4 - Order Integration
|
If you would like a live demo of our Integration
Bridge, please contact
us.
* Price List integration works with standard pricing in
Microsoft Dynamics GP. Volume discounts are not currently
supported.
|