• lflugo
  • NEWBIE
  • 0 Points
  • Member since 2014
  • Technology Specialist
  • The Spitfire Group


  • Chatter
    Feed
  • 0
    Best Answers
  • 1
    Likes Received
  • 0
    Likes Given
  • 2
    Questions
  • 1
    Replies
If you try to run an sfdx soql query on a Windows terminal, PS, CMD, etc, you will get the following error if your profile contans spaces in the path:
PS C:\sfdx\project1> sfdx force:data:soql:query --query "select count() from Contact"
'C:\Users\Luis' is not recognized as an internal or external command,
operable program or batch file.
To work around this, set your LOCALAPPDATA environment variable to the eight character equivalent of the path segment that contains the spaces. For example, in my case, I set LOCALAPPDATA to C:\Users\LUISLU~1\AppData\Local:
PS C:\sfdx\project1>$Env:LOCALAPPDATA = "C:\Users\LUISLU~1\AppData\Local"
PS C:\sfdx\project1> sfdx force:data:soql:query --query "select Name from Project__c"
NAME
─────────
Project 1
Total number of records retrieved: 1.
I have used other sfdx commands without problems, but apparently, force:data:soql:query uses the LOCALAPPDATA environment variable when executing the command.
 
  • February 16, 2018
  • Like
  • 1
You cannot create a managed package that includes a custom report type with a Campaign with a related Contact object and install it on a Professional Edition organization. There is no indication during beta deployments that this will fail and the managed package uploads without errors and installs on other dev orgs. Unfortunately you can't correct this on your own because you cannot delete the custom report type that is causing the installation failure which makes the managed package unusable since you can use it to update existing installations. The only thing I have been able to do is create an unmanaged package without the custom report type and associated reports, install on a new dev org, and create another managed package with a different object prefix.

Does anyone have an alternate workaround for this issue, or is there a way that Salesforce can remove the custom report type from the released managed package so I can continue to use the existing managed package?

 
  • December 15, 2014
  • Like
  • 0
If you try to run an sfdx soql query on a Windows terminal, PS, CMD, etc, you will get the following error if your profile contans spaces in the path:
PS C:\sfdx\project1> sfdx force:data:soql:query --query "select count() from Contact"
'C:\Users\Luis' is not recognized as an internal or external command,
operable program or batch file.
To work around this, set your LOCALAPPDATA environment variable to the eight character equivalent of the path segment that contains the spaces. For example, in my case, I set LOCALAPPDATA to C:\Users\LUISLU~1\AppData\Local:
PS C:\sfdx\project1>$Env:LOCALAPPDATA = "C:\Users\LUISLU~1\AppData\Local"
PS C:\sfdx\project1> sfdx force:data:soql:query --query "select Name from Project__c"
NAME
─────────
Project 1
Total number of records retrieved: 1.
I have used other sfdx commands without problems, but apparently, force:data:soql:query uses the LOCALAPPDATA environment variable when executing the command.
 
  • February 16, 2018
  • Like
  • 1
You cannot create a managed package that includes a custom report type with a Campaign with a related Contact object and install it on a Professional Edition organization. There is no indication during beta deployments that this will fail and the managed package uploads without errors and installs on other dev orgs. Unfortunately you can't correct this on your own because you cannot delete the custom report type that is causing the installation failure which makes the managed package unusable since you can use it to update existing installations. The only thing I have been able to do is create an unmanaged package without the custom report type and associated reports, install on a new dev org, and create another managed package with a different object prefix.

Does anyone have an alternate workaround for this issue, or is there a way that Salesforce can remove the custom report type from the released managed package so I can continue to use the existing managed package?

 
  • December 15, 2014
  • Like
  • 0