วีดีโอ

I have opened a sales force account,but i don't see the change set option after expanding environment

Thanks for this Rob; N.B. Illuminated Cloud users have similar capability (log analyzer with visual tools)

very insightful!

Woow :) Thank you so much Jon for sharing your experience.

How to get that Trail Blazer hoodie jacket

Thanks Jack and Alba! Very helpful as we begin to navigate this new frontier for our clients.

❤️

Please invite Rene winklemeyer on podcast

I don't see the Experience Bundle Component metadata type when running a comparison in Gearset, what am I missing?

Thank you for this excellent video. One thing that does confuse me with the development process that you specified with Flows, where the Flows are *draft* until they are deployed to production, is that if the Flows are draft then the logic they contain won't be run by pre-deployment unit tests, which is surely very dangerous. If you had some unit tests that checked the state of an Account record after an account record is changed (because, say, you had some Apex Trigger logic) and you added additional on-Account-change logic via a record-triggered Flow then we want to be sure that we still get the expected Account end state, even with the additional Flow logic. But if the Flow is draft until after it is deployed to production, this surely won't be the case.

Awesome! Proud to see a young woman of color accomplish such an honorable distinction. Let your light shine bright Nadina Lisbon.

Worth noting that Data Cloud, Mulesoft, SFDC Connect are all extra cost licenses for the typical SFDC org

Thanks for the awesome info!!!!

Where does Gearset stores those backed up data from Salesforce

I give credit to UX for sure. I came from Copado background, which i hate today after going thru Gearset. Gearset has a very low learning curve. We can build a pipeline in min's where as Copado takes hours to days. In simple terms, Copado sucks compared to Gearset. Good job guys.

can we have multiple sources like feature branches and a single target like SB/org ?

I figure it is very helpful for release management. But is it beneficial to developer as well? I wonder if once you decide to use all developers have to use this tool?

Can this be used to deploy from a production org to another production org?

When I am trying to test my LWC Component. It throws me this error in terminal >lwc-jest error Invalid sourceApiVersion found in sfdx-project.json.Expected 47.0, found 45.0

Very cool

Can you please share the details

good work ...keep it up:)