Try it
How can we help?

Search for answers or browse articles about Sintel Apps

< All Topics
You are here:

JavaScript API Differences Between Sintel Forms and Sintel Apps

Posted
Updated
ByMichał Gołka
1.5 out of 5 stars

1 rating

5 Stars 0%
4 Stars 0%
3 Stars 0%
2 Stars 0%
1 Stars 100%

Sintel Apps replaces the legacy Sintel Forms SharePoint Add-in with a modern SharePoint Framework (SPFx)–based architecture. This change aligns the platform with Microsoft’s current development model and improves compatibility with modern SharePoint environments.

 

As part of this transition, several JavaScript API methods have been updated or enhanced to better reflect the capabilities and patterns of the new SPFx-based implementation. The following sections highlight the key differences developers should be aware of when migrating existing Sintel Forms solutions to Sintel Apps.

 

Key JavaScript API differences:

 

No. Sintel Forms Sintel Apps
1 getValue (Person field)

Returns an array even for single-select Person fields.

 getValue (Person field)

Returns a single object for single-select fields:

{ emailAddress: "a@a.com", displayName: "Joe Bloggs" }
2 getValue / setValue

Generic methods used for most field types.

 getValue and setValue still work, but it is recommended to use field-specific methods:

  • getTextFieldValue / setTextFieldValue
  • getNumberFieldValue / setNumberFieldValue
  • getBooleanFieldValue / setBooleanFieldValue
  • setLookupFieldValue
  • setUserFieldValue
  • getRelatedListFieldValue / setRelatedListFieldValue
3 getUserProperties, getUserProfile getUserProperties

The API has been simplified to a single method.

const requesterEmail = getValue("Requester")?.emailAddress;

if (requesterEmail) {
    getUserProperties(requesterEmail).then(data => {
        setValue("Email", data.Mail);
        setValue("Manager", data.Manager);
    });
}
4 getFilteredFirstListItem
getFilteredListItems		 getListItems

A single API method replaces the previous filtered list retrieval methods.

getListItems({
  listInternalName: "Projects",
  search: {
    value: "Yes",
    fieldInternalName: "Program",
    operator: "equals"
  },
  itemsLimit: 0,
  returnedFieldInternalNames: ["ID","Title"]
})
.then(result => {
  const mappedResult = result.map(item => ({
    id: +item.ID,
    value: item.Title
  }));
});
5 addCustomButton addTopBarButton

A single API method replaces the previous filtered list retrieval methods.

/**
 * Adds a custom button to the form's top bar.
 * @param label - The label of the button.
 * @param icon - The icon of the button (name of the [Font Awesome icon](https://fontawesome.com/icons)). Can be `undefined` for no icon.
 * @param action - The action to perform when the button is clicked. Can be:
 *                 - A string representing a URL to navigate to.
 *                 - An object with `url` and optional `target` properties for navigation.
 *                 - A callback function to execute custom logic.
 */
addTopBarButton: (
    label: string,
    icon: string | undefined,
    action: string | { url: string; target?: string } | (() => void),
) => void;
6 updateLookupValues updateLookupOptions

A single API method replaces the previous filtered list retrieval methods.

updateLookupOptions: (
    fieldInternalName: string,
    values: LookupValue[] | undefined,
    listInternalNameOrId?: string,
) => void;

IMPORTANT: values require capital ID, e.g.. {ID: 1, value: ‘Option 1’};

 

For detailed examples of how to use the Sintel Apps Public JavaScript API within Logic rules, see Using the JavaScript API in Logic.

Was this article helpful?
1.5 out of 5 stars

1 rating

5 Stars 0%
4 Stars 0%
3 Stars 0%
2 Stars 0%
1 Stars 100%
5
Please Share Your Feedback
How Can We Improve This Article?
Table of Contents