Hi guys I am facing issue saml assertion flow I done with SSO (single sign on ) I got 2.0 oauth endpoint url I want access token
I tried with Salesforce docs help but is showing sever error 500 try cut some characters and insert it. And maybe invalid grant type please give any example
#Integration #Desktop Integration #Continuous Integration #SFDC Integration #System Integration
Hello,
I'm facing issues with Org-wide email addresses. I have Workflow alerts that uses Org-wide email addresses and also Apex classes that sent email using code like this email.setOrgWideEmailAddressId(System.Label.OrgWideEmailAddressId);
When pushing those components on the scratch org, workflow Alert fail. The Apex classes can deploy but test run are failing because the Org-wide email address do not exists.
I understand that I need to create the org-wide email address on the scratch Org and open the specified mail box and click the link to validate the address in Salesforce. The question is how to do this as part of Continuous Integration where I'm creating scratch Org on the fly and pushing code on it and then running Test classes?
Is somebody facing the same Issue? is there a workaround for this?
Any help will be highly appreciated.
Thanks
@Patrick Fischer What is your goal here? I don't understand why you're replying with:
<senderAddress>OWEA1</senderAddress>
<senderType>CurrentUser</senderType>
This will deploy fine to any environment, i.e.
scratch-orgs and sandboxes
and
The good thing is, that the script takes & replaces
emails by environment. Example: a) for Scratch-Org / Dev
Sandbox it's 'CurrentUser'
Unless I'm missing something obvious, both of these are misleading claims. "OWEA1" is an invalid email address and can't be deployed to any environment. And "CurrentUser" is an invalid email address and can't be deployed either.
For deploying to new scratch orgs that can't have any verified email addresses set, neither of your messages seem to work.
Where is the April #SFDevsAMA?
Heads up, developers! Our regularly scheduled Ask Me Anything livestream will be in person at TrailblazerDX this month. We’d love to see you there! Register for TrailblazerDX now if you haven’t already to join us in person for this session.
This session will cover all things #Continuous Integration and feature experts @Shane McLaughlin, @Philippe Ozil and @Alba Rivas. You won’t want to miss it!
If you’d like to submit a question in advance, drop a comment on this post or tweet your question using the hashtag #SFDevsAMA.
When: Wednesday April 27 from 4:30-5:10 p.m. PST.
Where: Moscone Center, Platform Theater, San Francisco
Starting in 30 Minutes: #AskMeAnything with the Salesforce Developer Advocates!
Our experts today are Kevin Poorman and Philippe Ozil, and they'll be answering all your questions on CI/CD and DevOps.
To participate:
See you soon!
#CICD #Devops #SFDX CLI #Salesforce CLI #Continuous Integration #Continuous Delivery #Continuous Deployment #TrailblazerCommunity
Question from venkyonutube1 on YouTube: Off topic for today's session. What happened to Code builder? Will it be GA anytime soon? is there any way to create or edit LWC on a browser based tool?
TOMORROW January 26th: ASK ME ANYTHING with the Salesforce Developer Advocates!
Join Salesforce Developer Advocates Kevin Poorman and Philippe Ozil here for our monthly feature, Ask Me Anything! This 1-hour session is your chance to get the answers you need to succeed. Bring your questions!
Click here to add it to your Google Calendar. This event will feature a live session from our YouTube channel and the developer advocates will answer questions that you post here using the official #SFDevsAMA tag. The live stream link will be shared on this page just before the event goes live.
#CICD #Devops #SFDX CLI #Salesforce CLI #Continuous Delivery #Continuous Integration #Continuous Deployment
Hello! We recently switched over from metadata format to source format in our source control (Github), and created new CI/CD pipelines in Azure to handle source format builds and releases. Since we made that change though, I've been finding that every Continuous Deployment release to our sandbox orgs is creating a new version of our flows and processes, even though those flows were not actually changed/updated in the release.
Since we have multiple builds a day being released, flow versions are rapidly proliferating and we have started hitting the "too many flow versions" error on our releases due to hitting 50 versions on certain flows.
Previously, our flows did not have an "API Version for Running", but all of the new versions that are automatically created show an API Version for Running of 49.0. I am not sure why they are getting added as 49.0 instead of our current org API version 51.0. I have read this stackexchange thread on the topic, which suggests that perhaps adding the current API version of the target environment to the flow-meta.xml file would resolve the issue, but I am wondering if there is a different solution that wouldn't require us to always use the latest api version for all of flows.
Gotcha.
The invocable actions fix is in review right now, so it'll probably be in production sometime this month. The fix is being performed by a different team so I don't have full details, but I've subscribed to alerts on the work item and will update once I hear more.
Has anyone here achieved a continuous integration for Salesforce with TeamCity? I am struggling to configure the build configuration for TeamCity for Salesforce deployments - so any help (and preferably detailed steps) would be much appreciated
Anyone have tips on doing SFDX / Continuous Integration on Azure DevOps "Build Pipelines"?
I didn't see it listed on @Karen Fidelak 's recent blog post
In this trailmix, in the advanced level section. Two of the links go to the same page.
links: Continuous Integration and Continuous Delivery
Anyone been able to run tests within a scratch org as a separate user created in the scratch org via the CLI?
We require the running user to have a particular setup in order for tests to run correctly. We're able to create the user via the CLI, but when we attempt a 'sfdx force:apex:test:run -u <username here>' we get 'Unable to invoke async test job: expired access/refresh token.'
If I attempt to authorize the newly created user with the devhub via 'sfdx force:auth:jwt:grant ...' we receive 'invalid_grant - user hasn't approved this consumer'.
All of this is being done as part of our continuous integration script - so would love to hear if anyone has an idea on how to work through this.