Business Rules vs. Client Script. Business Rules work on the Server (mostly). Client Script works only on the Form. If you import data via API, Client Script won't run. Business Rules (usually) will. For data integrity, always prefer Server-side logic.
#Logic #Architecture #D365
Posts by GIGS.TECH
Sunday Habit: Check the "GIGS.TECH" board. We drop new roles on Monday mornings. If you scan it Sunday night, you can prep your cover letter and be the first application in the inbox at 9 AM. Speed wins.
#JobBoard #Hiring #GIGSDOTTECH
Relationship Mappings. When you create a record from a parent record (e.g., New Contact from Account), you can map fields to auto-populate. This is the oldest feature in CRM (from 2011!), and people still forget it and write JavaScript to do it. Respect the classics.
#DynamicsCRM #OldSchool #NoCode
Love your job? β€οΈ If yes, tell your manager. People often only speak up when they are unhappy. "I really love working on this PCF project" puts you in line for more of that work. Manage your career joy.
#CareerAdvice #Valentine
Dataverse "Formula Columns" (Calculated fields 2.0). They run on Power FX! They are calculated in real-time (not async like Rollup fields). They are much faster than the old "Calculated Fields." If you need simple math (Price * Qty), use Formula Columns.
#Dataverse #PowerFX #TechUpdate
Friday the 13th for Recruiters: Receiving a resume in .txt format. π± Receiving a resume with a photo of you at a bar. Receiving a resume named "Resume_Final_v3_EDIT_REAL.pdf". Don't be the horror story.
#ResumeFail #JobSearch
App Insights. Connect your Power Apps to Application Insights. It gives you telemetry on user behavior. "Nobody is clicking the 'Submit' button." Maybe it's because the button is off-screen on an iPad? App Insights tells you what users do, not what they say.
#Telemetry #UXResearch #PowerPlatform
Salary vs. Equity. πΈ In the Dynamics world, equity is rare unless you join an ISV (Product company). For consultancies, Cash is King. Don't take a lower salary for "profit share" unless you have seen the books. Demand market rate.
#Compensation #TechJobs
Summary: To move up, you have to zoom out. Stop obsessing over pixels and start obsessing over architecture.
#CareerGrowth #Mentorship #GIGSDOTTECH
Stage 3: The "Ecosystem Architect"
- Focus: "I can design a secure, scalable system that costs less to maintain."
- Tools: Fabric, Governance, Custom Connectors, PCF.
- Reality: You write less code, but you make bigger decisions.
Stage 2: The "Solution Consultant"
- Focus: "I can map the business process to the technology."
- Tools: Model-Driven Apps, ALM, Security Roles.
- Trap: You rely too much on "Out of the Box" and fear code/Azure.
- Escape: Learn Azure Integration (Logic Apps/Functions).
Stage 1: The "App Maker"
- Focus: "I can make the button turn red."
- Tools: Canvas Apps, SharePoint, basic Flows.
- Trap: You get stuck building simple forms and never learn data modeling.
- Escape: Learn Dataverse.
The 3 Stages of a Power Platform Career (and how to get unstuck) π§΅
Most people plateau at Stage 2. Here is how to break through to Stage 3.
D365 Sales "Sequences" (Sales Accelerator). This is replacing standard "Workflows" for lead nurturing. If you are still building complex Power Automate flows to create tasks for salespeople... stop. Use Sequences. It gives them a UI checklist. Itβs built-in. Use standard features first.
The "Why us?" question. Don't say "Because you are a big Microsoft partner." Say "Because I saw you delivered the [X] project for [Client Y], and I specialize in that vertical." Flattery works, but researched flattery works better.
#InterviewTips #Research
Power Pages "Anonymous" Access. Be careful. If you enable "Anonymous" on a table permission, you are exposing that data to the public internet. Always double-check your OData feeds and Liquid templates. One wrong permission = Data Breach.
#Security #WebDev #PowerPages
Contract Renewals. If you are a contractor and your contract ends in March, start talking NOW. Feb 9th is the sweet spot. "I'm enjoying the project and wanted to discuss plans for Q2." Don't wait until March 15th.
#Freelance #Consulting #Business
Power Automate: Trigger Conditions. Stop triggering your flow on every modification and then using a "Condition" action to stop it. That counts as a flow run ($). Use Trigger Conditions (the expression at the top) to stop it from ever starting. Save money. Save API calls.
Don't stress about "Imposter Syndrome." The platform changes every week. Nobody is an expert in everything anymore. We are all just professional Googlers who know how to read documentation. Confidence comes from the ability to find the answer, not knowing it instantly.
#MentalHealth #TechLife
XrmToolBox "Attribute Usage Inspector." Ever wonder "Can I delete this field?" This tool tells you exactly how many records are actually using that field. If it's 0% populated, delete it. Keep your schema clean.
#DataHygiene #AdminTools #D365
Saturday project: Clean up your LinkedIn "Skills" section. Delete "Microsoft Word." Delete "Internet Explorer." Add "Copilot Studio," "Power FX," "Fabric." The algorithm matches candidates based on these tags. Keep them fresh.
#LinkedInOptimization #Career
Power BI "Direct Query" vs "Import." Direct Query sounds great ("Real time data!"). But it kills performance for the user. Always default to Import unless you strictly need second-by-second updates. Fast reports > Live reports.
#PowerBI #DataViz #Performance
The "Ghost" Job. π» Some job postings are just there to collect resumes for the future. How to spot them:
- Posted 30+ days ago.
- Very generic description.
- No hiring manager listed. Focus your energy on "Posted 3 days ago" with a "Hiring" badge.
#JobSearchStrategy #Recruiting
Dataverse Search (Relevance Search). Enable it! The standard "Quick Find" is archaic. Dataverse Search gives you the fuzzy matching, global search, and performance of Azure Search without the setup. Itβs a toggle. Flip it.
#Search #UX #D365
Don't ignore the "Functional" questions in a "Technical" interview. "How would you explain a 'Many-to-Many' relationship to a user?" This tests your communication skills. Don't draw an ERD diagram. Use an analogy (Students vs. Classes).
#SoftSkills #TechCommunication
4/ Why this fails It fails when the Pro Dev tries to rewrite the UI ("It's ugly") or the Citizen Dev tries to write complex SQL plugins ("I can do it myself"). Stay in your lane. Respect the other lane.
#FusionTeams #Agile #Microsoft
3/ The Deployment The Pro Dev owns the Pipeline. The Citizen Dev commits to a branch (or uses the simplified pipeline deployment). The Pro Dev reviews the PR (Pull Request).
2/ The Interface The Pro Dev builds an "API Facade" (Azure API Management or Custom Connector). The Citizen Dev consumes that connector. They never touch each other's code.