When to use this endpoint

Use PowerBI_getUserSkillsData as the join table between the Users and Skills Power BI datasets.

Authentication and permissions

The request must authenticate with signed API-key fields or a logged-in CRM session so that the tenant database and user context are available. The handler performs no page or role-permission check.

This direct dataset route does not consume the unsigned api_id/api_key pair used by the Power BI connector. Use PowerBI_getData for the self-authenticating connector feed.

Parameters

This endpoint has no operation-specific parameters.

Example request

FM_api('PowerBI_getUserSkillsData');

Example response

[
  {"id":"31","user_id":"18","skill_id":"7","skill_multiplier":"1.5"}
]

Errors and unusual responses

ResponseCondition
{"error":"not logged in"}No authenticated tenant context is available. Invalid signed credentials can be rejected by the dispatcher before the handler runs.

Legacy application errors may be returned with HTTP 200. Check the decoded response for error, not only the HTTP status.

Behaviour and edge cases

  • Returns exactly id, user_id, skill_id, and skill_multiplier from every assignment row.
  • The helper does not join or filter user/skill records, so assignments for inactive users or missing lookup rows can remain in the output.
  • There is no explicit ordering, search, or pagination.
  • The aggregate feed exposes the array as user_skills for module=user_skills and includes it in module=all.

See it in Fieldmotion

CRM1

The legacy connector uses this as the User Skills join table.

CRM2

CRM2 does not call this reporting route for user-skill editing.

Related endpoints