The System Services page is used to define those dynamic filters that will be used to retrieve data from the ERP.
Title User defined name of the filter.
ERP Select appropriate ERP
Primary Filter Service This will be the webservice, view or SQL table to be referenced. It will be the ODATA endpoint resource name.
Email Field The field containing the users’ email addresses that will be leveraged to retrieve the filter key.
Filter Key The field that will serve as the key and be used to filter the data retrieved (ie: Customer No or Vendor No)
Services
The Services page is used to configure those services that present the data desired. See Service Configuration for detailed instructions for service setup.
RS Configurations
The RS Configurations section is short for Report Service configuration and is used to enable users to generate various reports from within the portal.
Report Service Configuration
There are multiple types of reporting integrations available to the portal. With example configurations, they are as follows:
NAV – On premise Business Central reports
SSRS – SQL Reporting Service Reports
Power BI – Power BI reports
Image – An image that is to be associated to a service and rendered in the portal
SP Document Library – A SharePoint document library that is to be rendered in a web part and displayed as filtered in the portal
Title User defined name
Report Service Provider Select the appropriate report, image or document library desired for portal integration
Report Service URL URL of the deployed print, report or image service
Report Function/Path Location of the Report
Report Published Location Defines the location of where the report will be published. This will be a local shared drive.
Show Open/Save Prompt Allows user to save the report vs. immediately opening in browser
Report Parameter Configuration
Internal Name The internal name of report parameter found in the report
Value Source Applicable ERP options are as follows
Column – Parameter is passed from an associated service
Constant – A constant value is defined for the report parameter
Token – A token variable will be passed from various sources. If this option is selected, a Value Type field will become available, with the following options:
While most of the token options are self explanatory, the DyamicPoint.Mapped value type is the most flexible as it will retrieve a parameter dynamically from a service filtered by a system service. An example configuration is as follows:
Value The corresponding field from the Portal service or constant value used to populate the parameter
Webhooks
The Webhooks page is used to enable connection to Microsoft’s Power Automate.
Fields
Title User defined name of the webhook.
Service This is a drop down of the configured services. This is the service that the webhook is to be associated with.
Action The following options are available and will determined the point of time that a http request will be made in relation to the various actions within the Portal.
None
View
Edit / Save
Create
Submit
Print
Pay
Trigger URL This will be the HTTP post url supplied in Power Automate
Service Fields The names of the fields that will be passed in the schema
Service Line Item Fields The names of the line item fields that will be passed in the schema
Include User Name Select if user name is desired to be included in schema
Include Email Select if user email is desired to be included in schema
Delay Integration Select if you’d like to delay the integration until after a Power Automate workflow has been completed. Details of this configuration can be found in the Delay Integration section.
