[TIPS] Move to Required Stage Automatically in Dynamics 365 Business Process Flow

 Move to Required Stage Automatically in Dynamics 365 Business Process Flow

[TIPS] How to Set OData Style Filter in Power Automate Flows

 [TIPS] How to Set OData Style Filter in Power Automate Flows

[TIPS] Notifications within Power Apps

Notifications within Model-driven apps and Canvas apps

[TIPS] How to check if filter result is null or vacant

 [TIPS] How to check if filter result is null or vacant

[TIPS] Add new line to the string / String concatenate with new line in Power Apps Canvas App

 Add new line to the string / String concatenate with new line in Power Apps Canvas App

SSIS, Dataflows, ADF (Azure Data Factory)

 SSIS, Dataflows, ADF (Azure Data Factory)

How Service Protection API Limits are enforced

How Service Protection API Limits are enforced

 Reference

Service protection API limits are enforced based on three facets:

  • The number of requests sent by a user.
  • The combined execution time required to process requests sent by a user.
  • The number of concurrent requests sent by a user.

If the only limit was on the number of requests sent by a user, it would be possible to bypass it. The other facets were added to counter these attempts. For example:

  • You could send fewer requests by bundling them in batch operations.
    • The combined execution time limit will counter this.
  • Rather than sending requests individually in succession, you could send a large number of concurrent requests before service protection API limits are enforced.
    • The concurrent request limit will counter this.

Each web server available to your environment will enforce these limits independently. Most environments will have more than one web server. Trial environments are allocated only a single web server. The actual number of web servers that are available to your environment depends on multiple factors that are part of the managed service we provide. One of the factors is how many user licenses you have purchased.

The following table describes the default service protection API limits enforced per web server:




[TIPS] How to Install Power Query Connector in VS2019 SSIS

 [TIPS] How to Install Power Query Connector in VS2019 SSIS

[Demo] Control your TESLA through Siri and Power Automate

[Demo] Control your TESLA through Siri and Power Automate

Imagine a scenario: in a freezing cold winter, you are heading to the parking lot for your Tesla car. You are holding a big box and have no hand to take out the phone then choose the commands from the menus to turn on the AC remotely, or open the rear trunk. So you just talk to your Apple watch and tell Siri to command the car easily and promptly. Is it an interesting experience you wanna try? If so, you may follow the below steps to finish your personal control application.

Disambiguation operator in Power Fx

 Disambiguation operator in Power Fx

Reference 1 2 3

As operator in Power Fx

 As operator in Power Fx

Use the As operator to name a record in a gallery or record scope function, overriding the default ThisItem or ThisRecord. Naming the record can make your formulas easier to understand and may be required in nested situations to access records in other scopes.

A few controls and functions apply formulas to individual records of a table. To refer to the individual record in a formula, use one of the following:


Power Fx formula reference for Power Apps

 

Power Fx formula reference for Power Apps

Reference

SQL: Data type for image

 

SQL: Data type for image

Reference: 12

The ntexttext, and image data types will be removed in a future version of SQL Server. Avoid using these data types in new development work, and plan to modify applications that currently use them. Use nvarchar(max)varchar(max), and varbinary(max) instead.

SQL: VARCHAR vs NVARCHAR

 SQL: VARCHAR vs NVARCHAR



varchar is used for non-Unicode characters only on the other hand nvarchar is used for both unicode and non-unicode characters. Some other difference between them is given below.

SQL: VARCHAR(N) vs VARCHAR(MAX)

  SQL:  VARCHAR(N) vs VARCHAR(MAX)


When choosing data type, we should consider the database design, performance, compression, and indexes in mind.

We can define a specific range for the varchar (n) data type, and it is the recommended way to do so.
Varchar (n) can store up to 8000 bytes of data using varchar (8000) data type.
Varchar (max) can store data up to 2 GB.

SQL: CHAR vs VARCHAR

 SQL: CHAR vs VARCHAR

[TUTORIAL] Trigger a Microsoft Flow from a Custom Button in Dynamics 365

 

Trigger a Microsoft Flow from a Custom Button in Dynamics 365