Skip to main content

About Javi – Dynamics 365 Developer

About Javi – Dynamics 365 Developer

About Javi – Dynamics 365 Developer

Hi! I’m Javi, a passionate Dynamics 365 developer and Computer Engineer, working since 2021 to create solutions that make businesses more efficient. I love learning new technologies, solving challenging problems, and sharing my knowledge with others.

I’ve also taught various subjects to students of all ages, which helped me develop patience and the ability to explain complex concepts clearly. On this blog, I share tips, tutorials, and guides on Power Automate, Dynamics 365, and other tech tools to help both beginners and experienced users improve their skills.

My goal is simple: make technical topics easy to understand and provide practical solutions you can apply right away.

Comments

Popular posts from this blog

Dynamics 365 Web API: How to Perform Multiple POST or Upsert Operations

Dynamics 365 Web API: How to Perform Multiple POST or Upsert Operations Dynamics 365 Web API: How to Perform Multiple POST or Upsert Operations The Dynamics 365 Web API provides a powerful way to interact with data in a structured and scalable manner. Among its most efficient — yet often underutilized — capabilities is the ability to perform multiple record operations (batch requests) or upserts (insert or update) in a single call. This article walks you through how to correctly build URIs, structure JSON payloads, handle lookup bindings using @odata.bind , and understand how Dynamics 365 interprets and processes these requests internally. 🧩 1. What Is an Upsert Operation? An Upsert is a hybrid between two common database operations: Insert (POST): Creates a new record. Update (PATCH): Updates an existing record. Dynamics 365 automatically determines whether to insert or update based on whether a record with the specified Alternate Key already exists. ...

How to Fix “A binary operator with incompatible types was detected” in Power Automate

Fixing Power Automate Error – A Binary Operator with Incompatible Types When working with Power Automate , we often encounter errors that seem simple but can be quite confusing. One common error that many developers face when using List rows or filters in Power Automate is: Error: A binary operator with incompatible types was detected. In this post, I’ll explain why this error happens and how you can fix it quickly so your flows run smoothly. Why This Error Happens This error usually appears when you are trying to apply a filter query in a List rows action and you are comparing two fields with incompatible types. For example: Comparing a lookup field directly with a text value. Comparing an integer field with a string. In Dataverse, certain fields, like lookups , require you to use their GUID values in the filter. If the types don’t match, Power Automate throws the binary operator error. How ...

Dynamics 365 CRM – Managing Translations in JavaScript with RESX Files

Dynamics 365 CRM – Managing Translations in JavaScript with RESX Files Dynamics 365 CRM – Managing Translations in JavaScript with RESX Files In multi-language environments within Dynamics 365 CRM , it is common to display localized messages in alerts, pop-ups, or validation logic. A robust solution is to use .resx resource files together with Xrm.Utility.getResourceString in JavaScript. Retrieving a Translation The standard pattern to retrieve a translated message is: Xrm.Utility.getResourceString( namespace.localization.webResourceName, namespace.localization.messageKey ); webResourceName : the name of the .resx resource file, without specifying a language ID. Dynamics automatically loads the correct language based on the user’s settings. messageKey : the key defined in the .resx file that contains the translated message. Best Practices for Structuring Keys Organizing translations in a c...