Joaquin Attanasio

Joaquin Attanasio

Business Intelligence Consultant | Microstrategy Expert | Data Specialist

Other Articles:

Transaction Conditions in MicroStrategy

Share on linkedin
Share on facebook
Share on twitter
Share on whatsapp

Good morning to all, my dear colleagues! Once again I come here to this corner of #BestinMicro, an oasis in the beautiful madness that comes with being a MicroStrategy consultant, and where I hope to help you a little bit with the different experiences that are acquired.

This week we’re going to dig a little deeper into the transactional side. We’ve already learned the basics and how it works, but today we’re going to look at some of the other features that MicroStrategy’s transaction services have, so let’s get started!


Today I am going to tell you about a feature that allows us to have control over the user experience when interacting with our transaction dashboards.

You may have noticed that when you right-click on an object that has a transaction configured, the “Transaction Conditions” option appears.


This functionality, depending on which field it is, will give us different possibilities of field behavior. By this, I mean that we can disable, hide or validate the values that users are setting.


It is possible to assign several actions to control and combine several conditions that must be met before a specific action can be performed. For example, you can disable the sending of a transaction until the user has provided contact information in the form of a valid phone number or email address.


In other words… we can define the behavior of the document fields depending on the values of the fields involved in the transaction.

Anyway, let’s do some examples in the tutorial. Let’s say we have a sales document where a user can modify the “Discount” column for a certain product. But we want that, although all articles can be displayed, only those in the “business” subcategory can be modified. To do this, go to transaction conditions and select “disable” everything that does not belong to this subcategory:


Once this is done, we will see that, when running the document, it will not be possible to edit anything that does not meet the condition mentioned above:


For example, if we are going to use the hide functionality, we can set, for example, that until certain data has not been validated, the submit button does not appear, or whatever you invent with the most creative originality you can deploy on your dashboard.

In short, it is a feature that adds a bit of dynamism to the dashboards. And it is worth noting that with few options it also adds another layer of security to the transaction functionality, which is not a minor point when using these tools.

And you, did you know about this functionality? How do you use it? Do you have any design tips to share? I read you in the comments below! ¡Until next time!!


Deja un comentario

Your email address will not be published. Required fields are marked *

Business Data Master Logo

No te pierdas el


Explicaremos en detalle los contenidos y objetivos del Business Data Master


18:30 (GTM+1)



* Tu información será utilizada exclusivamente para contactarte en relación al Business Data Master. No hacemos spam ni compartimos datos con terceros.