Resco Cloud

Resco Cloud is an all-in-one business solution that is highly customizable, secure, feature-rich and 100% offline-ready.

This connector is available in the following products and regions:

Resco Cloud provides you with all-in-one business solutions that are highly customizable, secure, feature-rich, and 100% offline-ready. This connector enables operations that allow you to seamlessly create, read, update, and delete records.

Prerequisites

In order to use this connector, you will need the following:

• An organization at Resco Cloud or any affiliated product from Resco.
• You can sign up for a free 30-day trial here.
• A user account with schema access privilege or system administrator privilege.

How to get credentials

This connector uses Basic authentication. When creating a new connector (in Power Apps/Logic Apps), you'll be required to provide login credentials. You will be also required to select a server to use with this connector and the organization name you specified during sign up.

Getting started with connector

Simply add any Resco Cloud connector step to your flow and start accessing/changing data in your Resco Cloud organization. This connector allows you to perform basic data operations such as read/create/update/delete.

Known issues and limitations

Paging

The List records action returns a maximum of 1000 records. If you would like to get more records, you have to use the Skip token input parameter. The Skip token is not returned directly, but instead Next Link is returned which contains Skip token also. To resolve Skip token for the next List records action call, you can use the expression in Set variable step like:

{
    "inputs": {
        "name": "skipToken",
        "value": "@{if(empty(outputs('List_records')?['body/@odata.nextLink']),null,decodeUriComponent(substring(outputs('List_records')?['body/@odata.nextLink'],add(indexOf(outputs('List_records')?['body/@odata.nextLink'], '$skipToken='),11))))}"
    }
}

Triggers

Resco Cloud connector supports triggers for create, update, and delete operations. In case of advanced requirements, there is a workaround available using the server process event and invoking an HTTP request provided by "When an HTTP request is received". Simply create a new automated cloud flow, name it, and click skip to create an empty flow. Search for "Request" connector and add the "When an HTTP request is received" trigger. Set "Request Body JSON Schema" to accept the id parameter:

 {
    "type": "object",
    "properties": {
        "id": {
            "type": "string"
        }
    }
}

Under "Show Advanced Options" set method to POST. Save the flow to generate "HTTP POST URL".

Now you have to create a process to invoke trigger in your flow. Log into your Resco Cloud server, start the Admin Console, and select Processes from the menu. Click "New", enter a name for the new process, select the desired entity (e.g. Account), and the desired event (e.g. Record is created). Add StringList variable headers and add item Content-Type: application/json;charset=utf-8 to it. Add string variable body as "Format Text" with:

\{ "id": "{Entity.id}" \}

Then, add the function step Server.InvokeWebRequest with POST method. URL copied from "When an HTTP request is received" trigger and body variable.

Now, when you create a record of the specified entity type, the trigger activates.

Common errors and remedies

For cloud servers, make sure that you have specified the proper server under the Connection dialog. If not, you may get an Unauthorized error. For custom or on-premise servers, enter the URL including protocol and port (if applicable), e.g. https://mycompany.com[:8080]

FAQ

• Q: How to use List records input parameters? A: These are standard OData query parameters. The syntax for each input parameter is defined by OData specification. The only thing to think of is using logical names instead of display names. (e.g. Account -> account, Name -> name, etc.). Logical names can be found under Entities in the Admin Console.
• Q: How do I get a picklist label? A: Each picklist field returns 2 values:
  • Field - This is the picklist value
  • Field (Label) - This is the label for the picklist value.
• Q: How do I get a lookup label? A: Each lookup field returns 3 values:
  • Field - This is the ID (GUID) of the reference
  • Field (Label) - This is the label (primary name) of the reference.
  • Field (Type) - This is the target entity of the reference.
• Q: How do I set lookup field? A: When setting lookup fields, you have to construct a reference consisting of record type and record id.
  • From existing record in your flow, you can use OData Id
  • By creating logicalName:id expression
  • By creating logicalName('id') expression

Creating a connection

The connector supports the following authentication types:

Cloud Server

Auth ID: cloudServer

Applicable: All regions

Use a cloud server to access your organization.

This is not shareable connection. If the power app is shared with another user, another user will be prompted to create new connection explicitly.

On-premise Server

Auth ID: onPremiseServer

Applicable: All regions

Use an on-premise server to access your organization.

This is not shareable connection. If the power app is shared with another user, another user will be prompted to create new connection explicitly.

Default [DEPRECATED]

Applicable: All regions

This option is only for older connections without an explicit authentication type, and is only provided for backward compatibility.

This is not shareable connection. If the power app is shared with another user, another user will be prompted to create new connection explicitly.

Throttling Limits

Actions

Create a new record

Delete record

Generate report

Get current user

Get questionnaire

Get record

List questionnaires

List records

Update a record

Triggers

When an item is created-updated-deleted

Definitions

binary