• Sabrina Perardt 2
  • NEWBIE
  • 10 Points
  • Member since 2018

  • Chatter
    Feed
  • 0
    Best Answers
  • 0
    Likes Received
  • 0
    Likes Given
  • 0
    Questions
  • 2
    Replies
Hi, working my way through the Lightning Web Components Basics and have encountered a problem when pushing source files to dev edt. i have no issues pushin the ebikes app sourcefiles to scratch org as described in the previous steps but when it comes to the step descibed in Deploy Files the following happens:

from the ebikes-lwc folder i run this command:

sfdx force:source:deploy -p force-app -u <myusername>

this is the error log:

PROJECT PATH                                                                            ERROR
──────────────────────────────────────────────────────────────────────────────────────  ────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
force-app\main\default\flexipages\Product_Record_Page.flexipage-meta.xml                You can't change a Lightning Page's associated object.
force-app\main\default\objects\Product__c\Product__c.object-meta.xml                    0M01t000000i7OF does not exist or is not a valid override for action View.
force-app\main\default\layouts\Order_Item__c-Order Item Layout.layout-meta.xml          In field: field - no CustomField named Order_Item__c.Product__c found (29:26)
force-app\main\default\layouts\Product_Family__c-Product Family Layout.layout-meta.xml  In field: relatedList - no CustomField named Product__c.Product_Family__c found (58:19)
force-app\main\default\layouts\Product__c-Product Layout.layout-meta.xml                Parent entity failed to deploy
force-app\main\default\objects\Order_Item__c\fields\Product__c.field-meta.xml           referenceTo value of 'Product__c' does not resolve to a valid sObject type (88:13)
force-app\main\default\classes\OrderController.cls                                      Product__r.Name, Product__r.MSRP__c
                                                                                                    ^
                                                                                        ERROR at Row:2:Column:13
                                                                                        Didn't understand relationship 'Product__r' in field path. If you are attempting to use a custom relationship, be sure to append the '__r' after the custom relationship name. Please reference your WSDL or the describe call for the appropriate names. (5:16)
force-app\main\default\applications\EBikes.app-meta.xml                                 In field: tab - no CustomTab named Product__c found
force-app\main\default\classes\ProductController.cls                                    Invalid type: Product__c (62:32)
force-app\main\default\classes\ProductController.cls                                    Invalid type: Schema.Product__c (63:16)
force-app\main\default\classes\TestOrderController.cls                                  Invalid type: Product__c (16:9)
force-app\main\default\classes\TestOrderController.cls                                  DML requires SObject or SObject list type: Product__c (19:9)
force-app\main\default\classes\TestOrderController.cls                                  Field does not exist: Product__c on Order_Item__c (21:35)
force-app\main\default\classes\TestProductController.cls                                Invalid type: Product__c (6:9)
force-app\main\default\classes\TestProductController.cls                                Variable does not exist: products (8:9)
force-app\main\default\classes\TestProductController.cls                                Invalid type: Product__c (8:22)
force-app\main\default\classes\TestProductController.cls                                Variable does not exist: products (15:9)
force-app\main\default\classes\TestProductController.cls                                Invalid type: Product__c (15:22)
force-app\main\default\classes\TestProductController.cls                                DML requires SObject or SObject list type: List<Product__c> (22:9)
force-app\main\default\classes\TestProductController.cls                                Invalid type: Product__c (36:9)
force-app\main\default\classes\TestProductController.cls                                Invalid type: Product__c (37:9)
force-app\main\default\classes\TestProductController.cls                                Variable does not exist: products (38:29)
force-app\main\default\tabs\Product__c.tab-meta.xml                                     In field: fullName - no CustomObject named Product__c found
force-app\main\default\permissionsets\ebikes.permissionset-meta.xml                     In field: object - no CustomObject named Product__c found
N/A                                                                                     Exception while getting the Apex class for reference ProductController of type apexClass in file productTileList.js

at first i thought i was in the wrong folder but deploying to scratch org from the same folder is no issue. 
Would be helpful if someone has anything to comment here

(have successfully deployed a couple of different "hello world" lwc´s to this org so that seems to work at least)
Working on TrailHead Challenge... (https://developer.salesforce.com/trailhead/force_com_introduction/data_security/data_security_sharing_rules)

Tasks completed:
The custom object must be named 'Project' with a resulting API name of 'Project__c'.   Done
The Name field for 'Project' must be of type Text (not Auto-Number).  Done
The custom object 'Project' must have a custom field of type picklist named 'Priority' with a resulting API name of 'Priority__c'. Done
The role label should be 'Training Coordinator' with the resulting 'Role Name' of 'Training_Coordinator'. Note that you may already have this role in your role hierarchy from a previously attempted challenge.   Done
Set the organization wide settings to public read only.    Done

Here is where I think is the problem:
The sharing rule can be named anything.  
 
Create sharing rule under "Sharing Settings" under Project Sharing Rules..  Create a criteria based project sharing rule with Priority custom field equal to High.  Shared with role "Training Coordinator" as read-only access.


What am I missing?