Many of Catalina Technology’s stored procedures accept a field called @parms that is an XML field for configurable parameters to be passed. An example of this is below.
You can see that there is a parameter getting passed called “@parms”. In that is a XML string that contains one or more parameter. In this case, there is a single parameter called “ADDRID” and it is getting passed the value of “C%” so that it can return all addresses that start with a “C”
COVID-19 has made sending out invoices and getting paid has become a challenge. Catalina’s Account Central is a customer portal, for Dynamics SL, that allows customers to review statements, pay invoices or against their account, and manage their customer account in SL. All payments are through a PCI compliant payment processor. And all transactions are completely integrated with Dynamics SL
Because of COVID-19, sending out invoices and getting paid has become a challenge. Catalina’s SLQuickPay allows you to get paid quicker by lowering the barrier of entry for customers to pay. We can simply send out a request for payment link to the customer via email. All they have to do is click on the link and make a payment through a PCI Compliant payment page (no Payment Portal login required.)
There are several ways that you can send out a link:
Add a button to most any screen in SL
Invoice and Memo: Send a link to pay the invoice
Sales Order Management Screen: Most likely to do a payment entry to collect a down payment
Shipper Screen
Any other screen that you might want to request payment
Automatically send links out when invoices are generated in SL
Add a button on Catalina’s Account Central or Order Central products
Catalina’s evergrowing list of API’s for Dynamics SL increases your capabilities to integrate other systems and apps to SL quickly and easily with modern API technology.
Earlier today, I was asked if I could come up with a query that would allow you to bring back line items for a sales order. But create a numbering scheme for the line items that re-start for each new order number. So, example:
You can see below, that ORD1234 has 3 items, indexed 1,2,3. and ORD5555 has 2 line items indexed 1,2
OrdNbr
InvtID
LineIndex
ORD1234
IN82344
1
ORD1234
IN82341
2
ORD1234
IN82344
3
ORD5555
IN089723
1
ORD5555
IN0123998
2
I accomplished this by using the DENSE_RANK().
Here is sample code:
[code language=”sql”]
SELECT DENSE_RANK() OVER (PARTITION BY OrdNbr ORDER BY OrdNbr, LineRef) * 10 AS LineIndex
, OrdNbr
, LineRef
, InvtID
, QtyOrd
FROM SOLine
ORDER BY OrdNbr, LineIndex
[/code]
What I wanted to do in this was to show the order number, lineRef, invtID, and qtyOrd. But I wanted to show the LineIndex in increments of 10 that restarted for every time the OrdNbr changed. I have one of the orders that have multiple line items circled below.
Catalina’s SMS Central allows you to easily dispatch your field techs, salespeople, and others straight from your Dynamics SL without any special mobile apps. All using SMS messaging. Nothing to deploy, works on any phone, and easy to maintain.
Your people in the field can send updates as replies that will get automatically updated in your back office. They can even send pictures, GPS coordinates, and other attachments which will automatically be attached to the service call, quote, invoice, timecard, or any other screen in Dynamics SL.
1. Create a service call, quote, invoice, or any other type of record in Dynamics SL. SMS Central will send an SMS message to the appropriate person in the field.
2. Your person in the field receives the message and can respond. Those responses will automatically update Dynamics SL.
3. The field person can also take pictures, GPS coordinates, or other mobile files and attach them to the service call, quote, invoice, or other screen in Dynamics SL using just an SMS message.
4. That photo, or other attachment, automatically attaches to the appropriate record in Dynamics SL
5. All attachments and SMS communication are also stored in a web portal, allowing your field people to review history without needing any special app. Any browser on any type of device will work!
There are times when you just cant get RDP/Terminal server access to your servers to access the Dynamics SL thick client. Like when you are on a tablet or remote. That is where Catalina’s Sales Central for Dynamics SL comes into play. This allows you to access Dynamics SL Order Management, Customer Management, Inventory, and other modules through a cross-browser, mobile-enabled solution.
Sales Central allows you to do the following
Take orders from your desktop, laptop, tablet, and even phone
Search, view, edit, and create sales orders
Search, view, edit, and create customers
View inventory and availability
Take credit cards
Customize to suit your needs
Below is a demo we did at one of our webinars that does a brief walk-through of Sales Central. If you have further questions or would like to have a more in-depth demo, please contact us at sales@catalinatechnology.com.
This is an example of how to use Quick Query as a data delivery tool for external systems using Catalina’s API for Dynamics SL. This example is for those who want to use a SOAP based interface.
1.In Visual Studio, we select the Visual C# Template for a Windows Form Application. Our client will be named: client.ctDynamicsSL.quickQuery.
Note: you can call the Catalina web services from any type of client that is able to make http/https calls, but for this example, we will use a Form Application.
2.Add a reference to our Quick Query Web Service a.Right click on “References” and select “Add Service Reference”
b.On the “Add Service Reference” screen, click the “Advanced” button in the bottom left. (Image: qqcclient3.png)
c.On the “Service Reference Settings” screen, click the “Add Web Reference” button. (Image: qqcclient4.png)
d.On the “Add Web Reference” screen, enter in the URL to the web service.
Click the arrow button to discover the web service schema.
After the service definition loads, enter in a name to refer to this service in your client.
E.g.: ctDynamicsSL.quickQuery
e.Click the “Add Reference” button.
f.The new web reference will show up in your project.
3.Create code to instantiate an object referencing our web service.
a.I like to store values that are required in the Soap Header in the app.config file using System.Configuration, so we will first add a reference to the System.Configuration assembly. References -> Add Reference -> System.Configuration
b.Create a private variable to store the actual object and a property to auto create the instance if the variable is null. This get{} property will pull the required header values from the app.config
Now whenever we want to call a function in the web service, we just reference it like so: myQQObj.functionName().
4.Add the necessary elements for our main Form.
a.TextBox for typing in a QueryViewName (tbQueryViewName)
b.Button for a QueryViewName search (btnSearch)
c.Button for executing our search (btnGetQuery)
d.DataGridView for holding our search parameters (dgvFilters)
e.DataGridView for holding our search results (dgvQueryResults)
5.Add a popup form for QueryViewName searches.
a.The QueryViewName is the root of the Quick Query Service; they are names of SQL Views built in to SL. This is a required element, so let’s build an easy way to lookup them up.
b.Add another Form object to the project: queryViewsPopup.cs
c.Add a DataGridView to the new Form object.
d.Click on the little arrow at the top right of the Grid and add ctDynamicsSL.quickQuery.vs_qvcatalog as the Data Source.
e.For ease of use, edit the DataGridView Columns.
Move the QueryViewName column to the first position.
Change Name to “QueryViewName” we will use this to reference the cell later.
f.On our main Form, tie an EventHandler to open this form.
g.Add a CellDoubleClick Event Handler, to take the selected row and return the QueryViewName back to the tbQueryViewName on the main Form.
6.Setup Filters DataGridView
a.The Quick Query Service getScreen call requires 2 parameters: queryViewName, filters[]. The filters parameter is of type: ctDynamicsSL.quickQuery.queryFilter.
b.The Filters is an array of triplets holding 3 required fields:
name – This must match the name of a column in the query view)
value – This is the value we are to filter/compare against)
comparisonType – This is any valid SQL comparison operator. E.g.: =, <, >, LIKE, IN, NOT IN
c.Select the Data Source as ctDynamicsSL.quickQuery.queryFilter
7.The Quick Query Service, is a V2 service by Catalina Technology and by design uses a screen() object for most calls that replicate the SL screen. Create a private variable to hold an instance of the screen object for all of our subsequent calls to the service.
8.Write the code to call the web service, pass the parameters and tie the results to the Result DataGridView (dgvQueryResults)
9.Test our Web Service Client:
a.Find a Query View with our popup.
b.Enter in some filters then Search and View the Results
