Deploy and Access Your Lightning App
Learning Objectives
After completing this unit, you’ll be able to:
- Deploy your Lightning app and metadata to a Salesforce org.
- Assign the permission set that grants users access to the app.
- Confirm that users can open the deployed app in Lightning Experience.
Deploy to Your Org
In the previous units, you built the complete Asset Tracker app in your SFDX project. To deploy your app from VS Code, press Ctrl+Shift+P (Windows) or Cmd+Shift+P (macOS) to open the Command Palette. Then select SFDX: Deploy This Source to Org. Or you can ask Agentforce Vibes by prompting:
Deploy all of this project’s Asset Tracker metadata to my org. If the deployment fails, show the error messages and wait. Do not rewrite files unless I ask.
Read the deployment results carefully. A successful deployment result shows that these 10 metadata objects are now in your org.
- Tracked_Asset__c (Object)
- Tracked_Asset__c.Serial_Number__c (Field)
- Tracked_Asset__c.Purchase_Date__c (Field)
- Tracked_Asset__c.Status__c (Field)
- Tracked_Asset__c.Assigned_Owner__c (Field)
- assetForm (LWC)
- Tracked_Asset_Record_Page (FlexiPage)
- Tracked_Asset__c (Tab)
- Asset_Tracker (App)
- Asset_Tracker_User (Permission Set)
If there’s an error, share the error messages with Agentforce Vibes, and it can help you correct the metadata. For example, here’s a prompt that you can use if the first deployment fails.
Fix the failing metadata based on the deploy error. Then redeploy all Asset Tracker metadata together. If it fails again, show the error messages and wait.
Treat the deployment as successful only when all components deploy without any failures. Salesforce deployments typically roll back the whole transaction if any component fails, so you must redeploy all components in that deployment after you fix errors. A narrower redeploy can leave the tab, app, or permission set missing after a rollback.
Assign the Permission Set
After deployment, your app’s structure is officially live in Salesforce. However, users can’t access the app just yet. Remember that during the co-create phase, Agentforce Vibes created a permission set that grants access to the custom object, the object’s fields, the custom tab, and the Lightning app. You can only assign this permission set now that it is successfully deployed to your org.
Assigning the permission set to yourself first allows you to confirm everything works before rolling it out to other users. Confirm that Asset Tracker User permission set is in your org, and then ask:
Assign the Asset Tracker User permission set to me.
Whenever you’re ready for others to use the app, assign the same permission set to them. If a user reports that the app or its records don't appear, a missing permission set assignment is the likely cause.
Open Your App in Lightning Experience
With the app deployed and the permission set assigned, confirm the Asset Tracker app works as expected.
- To open the App Launcher, on the left side of the navigation bar, select the App Launcher icon
.
- In the Search apps and items box, enter Asset Tracker, and then open the app.
- Select the dropdown arrow next to the Tracked Assets tab, and then select + New Tracked Asset. For the Asset Name, enter
My First Tracked Asset, and then select Save. Your custom Tracked Asset record page opens.
- Test your assetFrom component. In the Serial Number field, enter
1234, and then select Save.
If the app opens and you can create and edit records through the form, your Asset Tracker app is ready. If it doesn’t appear in the App Launcher, confirm that the user has the Asset Tracker User permission set assigned.
During the co-create phase, Agentforce Vibes added an action override to the Asset Tracker app’s metadata so that the custom Tracked Asset record page appears instead of the standard record page layout. However, this app-scoped assignment only applies when a user opens a Tracked Asset record from inside the Asset Tracker app. Because you are building this project as a single, self-contained experience, this assignment is all you need for now. If you later want the form to appear universally, even when a record is opened outside the app, open the custom Tracked Asset record page in the Lightning App Builder and change it to an org-default assignment.
You’ve deployed the Asset Tracker app, assigned the Asset Tracker User permission set, and confirmed that users can open and edit records. In the next unit, you’ll improve the app’s functionality and refine its styling.