Monthly Archives: January 2012

Using a M3 List Api for a single hit

For M3 we have different APIs, most used are probably the list and get APIs. But what if you have a mashup and what you need is in a list API? Well you could just as well use the list API and bind to the first returned item. Or in fact you configure the MIDataService to only return the first result in the list.

Assuming there is an exact match you will get the expected data back. Say that you want to list customers and you pass in Infor, if infor isn’t a valid customer the list API will return whatever customer that comes after alphabetically.

My example will have an entry field for the customer to search for and a button that will trigger the List Event. In a real scenario this would probably be replaced with an event from a standard M3 form, like a CurrentItemChanged on a list or a detail form. Continue reading

SOAP Mashup with Bing search

In this post I’ll create a Mashup with the DataListPanel. Data will be retreived from the Bing search web service. Then I’ll format the result in the list with a datatemplate, a clickable uri and use the the Open event to launch a web page and I show you how to show a clickable Uri. The Open Event is available in Lawson Smart Office 10.0.1.

Prereq: In order to use the Bing search API (for testing) you need to register and get your own application ID as identifier. In my Mashup this ID is replaced with “BingApplicationID”. Register to get your ApplicationID Continue reading

Calling Web Services using Process Server

Process Server has had a mashup control since version 9.1.3, called TriggerPanel. It could be used to trigger a process flow without returning data from the flow itself.
In Lawson Smart Office 10.0.0 the TiggerPanel supports a synchronous call which means that it is possible to run a flow and bring in data from the process back to the Mashup.

In order for the mashup to be able to automatically generate a UI and to be able to create an object model that can be used for easy binding the XML has to be according to a specific schema.

The XML schema describes a Header section and any number of Detail sections. The service has to at least return an xml document with only the root. The root element name is ProcessResponseHeaderDetails. Returning no Xml at all will result in an error dialog informing that no data was returned from the service. Continue reading

Calling a Web Service using WS and REST Data Services

In Lawson Smart Office 9.1.3 we introduced the REST data service for mashups. In version 10.0.0 we introduced support for SOAP based web services. In 10.0.1 we introduced some new configuration options that will help you to connect to the web services out there.

There are different options available when consuming SOAP web services in Mashups.

1. Data Service and WS
2. Data Service and REST
3. Process Server with TriggerPanel Continue reading