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. ...

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...

SSIS (.dtsx in Visual Studio) vs XrmToolBox — Data Transporter

SSIS (.dtsx in Visual Studio) vs XrmToolBox — Data Transporter SSIS (.dtsx in Visual Studio) vs XrmToolBox — Data Transporter Technical Comparison and Practical Guide for Moving Data Between Dynamics 365 / Dataverse Environments Moving data between environments (dev → test → prod) is something every team working with Dynamics 365 / Dataverse does frequently. There are two common operational approaches: Classic SSIS (Visual Studio .dtsx packages with Data Flow, Lookups, Scripts, SQL staging, etc.) — an industrial ETL/ELT approach. XrmToolBox – Data Transporter (a lightweight plugin for copying records between organizations) — a manual, fast, developer-oriented approach. Below we break down the real differences, risks, and practical recommendations for each method. 1) Architecture and Philosophy SSIS (.dtsx in Visual Studio) ETL/ELT architecture: connect to sources (SQL, CSV, APIs), transform (Derived Column, Lookup, Script Component) and load into Dat...