Tip #1461: Big int data type is available in Dataverse

Sometimes, good news sneaks into our world undetected. Big int as a separate data type has been available in Dataverse for about two years now.

Tip #1460: Loops and ThisRecord in low-code plug-ins

This image shows a whimsical and colorful illustration where a large group of cartoon baboons are typing away on old-fashioned typewriters. The baboons, each showing various expressions of focus and frenzy, symbolize inefficient coding practices. In stark contrast, a confident and smiling 'Real Developer' stands in the foreground holding a magic wand, symbolizing modern and efficient coding methodologies. The background is filled with streams of code flowing into the sky, enhancing the contrast between outdated and advanced approaches to coding.

When you use loops like ForAll function in a low-code plug-in, ThisRecord will change its meaning from the table row associated with the plug-in run, to the row inside the loop. Disambiguating is fairly straightforward… once you know how.

Tip #1449: Formula columns love calculated columns

A digitally created image featuring a knight in full armor at dusk, holding a large shield designed to resemble a giant calculator with an illuminated display. The knight is poised for battle with a sword in the right hand. In the extended background, a dramatic and cloudy sky looms over a chaotic medieval battlefield scene, with silhouettes of other knights engaged in combat and fallen warriors scattered across the field, enhancing the surreal fusion of ancient warfare and modern technology.

Can’t return the data type you need from a formula column? Do your homework then create a calculated column that simply casts to the correct type.

Tip #1448: Never delete columns in translation

The background of the image is a blurred office setting with a clear focus on a large, slightly angled Excel spreadsheet in the foreground. The spreadsheet is filled with columns containing multilingual text to symbolize translations in Dataverse. One of the middle columns is highlighted with a dramatic red overlay and a bold prohibition sign (a circle with a diagonal line) to catch the eye immediately, symbolizing the rule against deletion. Above the spreadsheet, in a cautionary yellow, the text reads: "Caution: Never Delete Columns!" with a subtitle saying, "Essential Dataverse Translation Rule" to provide context to the viewer. The prohibition sign is mirrored in the upper corner of the image for added emphasis, and there's a faint overlay of a globe made up of various national flags on the lower side of the spreadsheet, indicating the international nature of translations. The overall color scheme uses stark reds and yellows against a professional, muted background to grab attention and convey the seriousness of the message. The design balances a professional tone with the dramatic flair needed for social media engagement.

Dealing with Dataverse translation file? Never delete columns. But you are free to delete rows and tabs.

Tip #1441: Owner is a user is a team

WARNING: Niche L400 tip ahead. tl;dr If you’re expect primary column name to be tablename + “id“, add an exception for systemuser and team tables – both will come back as ownerid in custom API. L400 If custom API has an output property of type EntityReference then, for example, for account (or any other “normal”) table, the […]

Tip #1440: Relative dates in sample data

We all enjoy flexing our Dataverse or Dynamics 365 skills from time to time. Many of us have meticulously crafted a demo instance from proverbial stone and blood. However, one of the challenges is keeping the data up-to-date. There’s nothing worse than displaying 20 tasks that are all overdue by four months. Fortunately, Dataverse offers […]

Tip #1438: Turn on auto search for lookups

Search and rescue dog running across snow field

Today’s tip is from Amey “Anything But Code” Holden. You can drop your priceless tip into our tipping jar too, thank you very much! I (Amey, not me – t.j.) often see users struggle with the confusing behaviour of lookups in model-driven apps. Typical sketch from an average week of consulting with model-driven apps looks […]

Tip #1433: How to list all Dataverse tables in style

Is there any way to export automatically or with a script a list of all the Dataverse tables in an organisation? From our good friend Shan McArthur came a multilayer answer (narrated and illustrated by The Enabler): One: We have a virtual entity called entities that will give you a list of all entities in […]

Tip #1432: Create records in Power Automate without mandatory fields

I really like mini truck stops when two or more MVPs brainstorm a random problem, usually because they are bored 😈. Help me understand scenarios where one would use a guid() expression in flow when creating new rows. Antti Pajunen What Antti left out was (reasonably) common wisdom that explicitly setting identifiers for new records […]

Tip #1425: Dataverse CSV import using alternate keys

Today’s tip is from Alex McLachlan (@alex_mcla), saving the day (no kidding – I used it the very next day after receiving the tip). You can be a hero too by emailing your tip to jar@crmtipoftheday.com! With the classic import experience, you couldn’t use a CSV import containing an Alternative Key column to update existing […]

M	T	W	T	F	S	S
				1	2	3
4	5	6	7	8	9	10
11	12	13	14	15	16	17
18	19	20	21	22	23	24
25	26	27	28	29	30

Power Platform
Dynamics CRM

Tip of the Day