In a previous post we created the database entries for a new eConnect node. We’re going to skip the .NET parts and go straight to eOne SmartConnect.

eOne Logo

SmartConnect has been evolving rapidly. As of this writing we are using version 20.

SmartConnect version 20.12.2.38

Version of SmartConnect used for this post

To make our new eConnect node visible in SmartConnect, we need to use the SmartConnect Node Maintenance window.

Click it. I dare you.

Click it. I dare you.

In this case I choose to make a new group for the node. So the first thing I do in the Node Maintenance window is create that new group.

The next button

The next button

Add a group

Add a group

We’ll see later where this new group comes into play.

Now we’ll add the node itself.

Adding a node

Adding a node

SmartConnect finds the parameters of the stored procedure for us. However, in this version, everything is type String. We’ll change some of those types.

We could also change the display names if we wanted. For example, BACHNUMB could display as Batch Name, etc. I am fond of the names I used for the stored procedure parameters, so I’ll leave them be.

Check off the required parameters

Check off the required parameters

Change field types as needed

Change field types as needed

So, our new group contains only one node, which gives us the ability to insert a transaction document into a batch.

We can now use the new node in a SmartConnect map. This is where you see the node group we added, our node display name, etc.

Create a new map using our new node

Create a new map using our new node

When we set up the mapping details you’ll see our fields.

Using our new fields

Using our new fields

Now you should be able to finish the map as usual, run it, and see an assembly batch in GP (Transactions, Inventory, Batches window).

Here ends today’s lesson. I hope it is helpful!

Leave a Reply

Your email address will not be published. Required fields are marked *

 characters available