| Appsplus panel macro confluence macro | ||
|---|---|---|
| ||
**Delete Before Publishing**
|
In this article
| Table of Contents | ||||||
|---|---|---|---|---|---|---|
|
Overview
You can use this Dynamics 365 Business Central Create Snap to ...create new users in the Business Central application for a specific entity.
Snap Type
The <Snap name> Dynamics 365 Business Central Create Snap is a Read/ Write/Parse/Transform/Flow/Format-type Snap that reads/fetches/writes/parses/executes/transforms/calls/creates…
Prerequisites
Valid client ID.
A valid account with the required permissions.
None.creates a user in the application.
Prerequisites
None
Support for Ultra Pipelines
Works in Ultra Pipelines.
...
Works in Ultra Pipelines if....
...
Does not support Ultra Pipelines.
Limitations
None.
Known Issues
None.
Snap Views
Type | Format | Number of Views | Examples of Upstream and Downstream Snaps | Description |
|---|---|---|---|---|
Input | Document |
Binary
Binary or Document
|
|
|
..
Requires |
user data |
as a JSON document. | |
Output | Document |
|
Binary or Document
|
..
..
| Writes the new user information for an entity. | |||
Error | Error handling is a generic way to handle errors without losing data or failing the Snap execution. You can handle the errors that the Snap might encounter when running the | |||
pipeline by choosing one of the following options from the When errors occur list under the Views tab:
|
|
Learn more about Error handling in Pipelines. |
Snap Settings
...
| data | {"features":["title","icon","rounded","collapsible","border"],"title":"Documenting Fields Based On Data Type/UI Element","titleColor":"#000000","titleColorBG":"#ff5c30","titleSize":"14","titleBold":true,"titleItalic":false,"titleUnderline":false,"lozenge":"Hot stuff","lozengeColor":"#172B4D","lozengeColorBG":"#fff0b3","height":200,"panelPadding":12,"panelColor":"#172B4D","panelColorBG":"#FFFFFF","borderColor":"#ff5c30","borderRadius":3,"borderStyle":"solid","borderWidth":1,"icon":"editor/info","iconPrimary":"#FFFFFF","iconSecondary":"#0052CC","newMacro":false} |
|---|
**Delete Before Publishing**
Choose from the following sentences to document specific field types.
Drop-down lists/Option Buttons (radio buttons):
You must list the LoV and describe them if their meaning isn't apparent. In this case, format the LoV in italics, regular font for the LoV's description. In either case, list the LoVs as a bullet list.
<State what the option should do in this field>. The available options are: <bullet list of LoVs>
Specify the Salesforce API to be used. The available options are:...Select the <category> that you want to use. Available options are...
* Option 1<italicized>. <third person singular form of the verb>
* Option 2<italicized>. <third person singular form of the verb>
Select the API that you want to use. Available options are:
Bulk API. Sends the Snap execution request details as a bulk API call.
REST API. ...
OR
Select one of the three following modes in which the Snap executes:
* Validate & Execute. Performs limited execution of the Snap and generates a data preview during Pipeline validation, then performs full execution of the Snap (unlimited records) during Pipeline runtime.
* Execute only. Performs full execution of the Snap during Pipeline execution without generating preview data.
* Disabled. Disables the Snap and all Snaps downstream from it.
Check boxes:
If selected, <Snap behavior>.
If selected, an empty file is written when the incoming document has no data.If selected, <behavior>. If not selected/Otherwise, <behavior>
Use "If not selected" if the first sentence is long.
If selected, the Snap uses the file path value as is. Otherwise, the Snap uses the file path value in the URL.
If selected, an empty file is written when the incoming document has empty data. If there is no incoming document at the input view of the Snap, no file is written regardless of the value of the property.Select to <action>
Use this if the behavior is binary. Either this or that, where the converse behavior is apparent/obvious.
Select to execute the Pipeline during validation.
Text Fields
Describe what the user shall specify in this field. Additional details, as applicable, in a separate sentence. Include caveats such as the field being conditionally mandatory, limitations, etc.
Enter the name for new account.
Specify the account ID to use to log in to the endpoint.
Required if IAM Role is selected.
Do not use this field if you are using batch processing.
Numeric Text Fields
Describe what the field represents/contains. Additional details, as applicable, in a separate sentence. Include caveats such as the field being conditionally mandatory, limitations, etc. Include special values that impact the field's behavior as a bullet list.
The number of records in a batch.
The number of seconds for which you want the Snap to wait between retries.
The number of seconds for which the Snap waits between retries.
Use the following special values:
* 0: Disables batching.
* 1: Includes all documents in a single request.
Notes in field descriptions
Confluence’s new editor does not allow nesting of most macros inside another macro, especially the Note/Alert/Warning/Info (Panel) macros inside a table macro and Excerpt macros inside Expand or Panel Macro+ macros. So, as a workaround use the Footnotes approach as mentioned below:
...
Assign numbers at the Note locations in the form of follow through phrases like See Note 2 below this table. or such.
...
| Info |
|---|
|
): Indicates a list that is dynamically populated based on the configuration.Field Name | Field Type | |
|---|---|---|
Field Dependency
Description | |
|---|---|
Label*
Default Value: | |
Business Central Create |
BC Create | String | |
None.
Specify a unique name for the Snap. You can modify this to be more specific, especially if you have more than one of the same Snap in your |
pipeline. |
| |
Entity*
Default Value: | |
N/A | String/Expression | |
Sampling Type is Number of records.
Enter the number of records to output.
fieldset Name
Specify advanced parameters that you want to include in the request.
Field 1*
Default Value: <value> or None.
Example: <value>
String
Debug mode check box is not selected.
Field 2
Default Value: <value> or None.
Example: <value>
String
None.
Snap Execution
Default Value:
Example: Validate & Execute
Dropdown list
N/A
Specify the OData entity object. | |||
Batch size
Default Value: 1 | Integer/Expression | Specify the batch size to create a number of users in a batch. | |
Timeout (seconds)
Default Value: 300 | Integer | Specify the timeout to determine whether the connection is alive and also the timeout when waiting for response through a socket. | |
Number of retries
Default Value: 0 | Integer/Expression | Specify the maximum number of retries to be made to receive a response. The number of retries are disabled if the value is 0. | |
Retry interval (seconds)
Default Value: 1 | Integer/Expression | Specify in seconds, the time period between retry attempts. | |
HTTP header | Use this field set to define the HTTP key-value pairs to pass to the Dynamics 365 Business Central instance. | ||
Key
Default Value: N/A | String/Expression | Specify the key for the HTTP header. | |
Value
Default Value: N/A application/json;odata.metadata=full | String/Expression | Specify the value for the HTTP header. | |
Snap Execution
Default Value: Validate & Execute | Dropdown list | Select one of the following three Snap execution modes:
| |
|
|
|
Troubleshooting
Error | Reason | Resolution |
|---|
Account validation failed.
The Pipeline ended before the batch could complete execution due to a connection error.
Verify that the Refresh token field is configured to handle the inputs properly. If you are not sure when the input data is available, configure this field as zero to keep the connection always open.
Examples
Excluding Fields from the Input Data Stream
We can exclude the unrequired fields from the input data stream by omitting them in the Input schema fieldset. This example demonstrates how we can use the <Snap Name> to achieve this result:
<screenshot of Pipeline/Snap and description>
...
| More than 6000 requests were made in 300 seconds. | You must decrease the batch size and retry. |
| Too many requests sent to Dynamics 365 For Sales endpoint. | All Snaps related to the Microsoft Dynamics 365 For Sales Snap include |
REST API service endpoint returned error result: status code = 400 | Reason phrase = BAD REQUEST, refer to the error_entity field in the error view document for more details. You typically receive this message when:
| Please check the values of Snap properties. Specifically:
|
Error 500
| Client secret is expired. | Generate new Client secret. |
Error 401 | Token is invalid | Provide a valid token and reauthorize the account. |
Examples
Downloads
| Info |
|---|
|
| Attachments | ||||
|---|---|---|---|---|
|
Snap Pack History
| Expand | |||||
|---|---|---|---|---|---|
| |||||
| Insert excerpt | XYZ Snap Pack | XYZ Snap Pack | |||
...
Related Content
...
Endpoint Doc Link 1
...
Endpoint Doc Link 2
...
...