*** Pushing v55.0 metadata with SOAP API v54.0 connection ***
DEPLOY PROGRESS | ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ | 0/36 Components
DEPLOY PROGRESS | ███░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ | 3/36 Components
DEPLOY PROGRESS | ███░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ | 3/36 Components
DEPLOY PROGRESS | ████████████████░░░░░░░░░░░░░░░░░░░░░░░░ | 14/36 Components
DEPLOY PROGRESS | ████████████████░░░░░░░░░░░░░░░░░░░░░░░░ | 14/36 Components
DEPLOY PROGRESS | ██████████████████████░░░░░░░░░░░░░░░░░░ | 20/36 Components
DEPLOY PROGRESS | ███████████████████████░░░░░░░░░░░░░░░░░ | 21/36 Components
DEPLOY PROGRESS | ███████████████████████░░░░░░░░░░░░░░░░░ | 21/36 Components
DEPLOY PROGRESS | ██████████████████████████████░░░░░░░░░░ | 27/36 Components
DEPLOY PROGRESS | ██████████████████████████████░░░░░░░░░░ | 27/36 Components
DEPLOY PROGRESS | ██████████████████████████████████░░░░░░ | 31/36 Components
DEPLOY PROGRESS | ██████████████████████████████████░░░░░░ | 31/36 Components
DEPLOY PROGRESS | ██████████████████████████████████░░░░░░ | 31/36 Components
DEPLOY PROGRESS | ██████████████████████████████████░░░░░░ | 31/36 Components
DEPLOY PROGRESS | ██████████████████████████████████░░░░░░ | 31/36 Components
DEPLOY PROGRESS | ██████████████████████████████████░░░░░░ | 31/36 Components
DEPLOY PROGRESS | ██████████████████████████████████░░░░░░ | 31/36 Components
DEPLOY PROGRESS | ██████████████████████████████████░░░░░░ | 31/36 Components
DEPLOY PROGRESS | ██████████████████████████████████░░░░░░ | 31/36 Components
DEPLOY PROGRESS | ██████████████████████████████████░░░░░░ | 31/36 Components
DEPLOY PROGRESS | ███████████████████████████████████████░ | 35/36 Components
DEPLOY PROGRESS | ███████████████████████████████████████░ | 35/36 Components
DEPLOY PROGRESS | ████████████████████████████████████████ | 35/35 Components
=== Component Failures [1]
Type Name Problem
───── ────────────
─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
Error Find_Schools School_Section1 (Screen Component) - Because the
"School_Section1" screen field on the "School" screen is a section, the
regionContainerType is required.
ERROR running force:source:push: Push failed.
Salesforce Org Type
Scratch Org
Function Language
No response
Steps To Reproduce
sfdx force:source:push
this repo source to a Functions-enabled scratch org.
Current Behavior
Salesforce throws an error.
Expected Behavior
Salesforce to complete the source deployment.
Relevant Log Output
No response
Code of Conduct
Summary
The "Browse The Docs" button does open Functions documentation in a new browser tab, but if there were any other pages visited in the "Home" page's tab before pressing the button, the effect will be as if you pressed the "back" navigation button in your browser. You can return the the "Home" page by pressing the "forward" navigation button in your browser.
Salesforce Org Type
Scratch Org
Function Language
JavaScript
Steps To Reproduce
Using Chrome on Mac
Follow all of the instructions in README to set up Functions Recipes in a scratch org.
Open "Sales" using the App Launcher
Open "Functions Recipes" using the App Launcher
Press the "Browse The Docs" button
Note that Functions documentation opens in a new browser tab
Close that documentation browser tab
Current Behavior
The browser window that had contained "Functions Recipes" Home screen is currently on "Sales" Home screen
Expected Behavior
The browser window should be open to the "Functions Recipes" Home screen.
Relevant Log Output
No response
Code of Conduct
Summary
The instructions in the README explain how to get Functions Recipes working in a scratch org, and they work. But, when I get Functions Recipes into a production org, some examples fail for lack of access to Account fields. For example, the "SalesforceSDK" recipe fails with this error: Function threw: Failed to insert record. Root Cause: No such column 'AccountNumber' on sobject of type Account
Suggested Solution
If you add the following explicit write permissions to the Functions permission set, the recipes behave correctly:
Account.AccountNumber
Account.Industry
Account.Type
Account.Website
Alternative Solutions
No response
Code of Conduct
Summary
Filing per-request of @schandlergarcia after chatting with him. If you check out this repo and switch to the java-recipes
branch on a Windows machine, all of the line endings are (by default) CRLF. If you then try to start any of the Java functions in a local Docker container, things fail because the Linux host doesn't know how to process those files. I was able to work around this by running dos2unix
recursively on the functions
directory.
Hopefully this is something that can be captured in the repo as-is, or perhaps this is just something that must be documented for folks on Windows, but it could be an impediment for Windows folks test-driving Java-based functions via this repo.
Salesforce Org Type
Scratch Org
Function Language
Java
Steps To Reproduce
Should be captured in the summary, but let me know if not.
Current Behavior
Java functions can't be started in Windows until line endings are changed from CRLF to LF.
Expected Behavior
Should work without requiring explicit line ending conversions.
Relevant Log Output
No response
Code of Conduct