I've documented here what I think is a defect with how SObjects are returned into a flow from an InvocableMethod: http://salesforce.stackexchange.com/questions/68718/returning-an-sobject-in-an-invocablemethod.
Basically when returning an SObject with field values queried into a flow, the field values are not accessible to the flow. The documentation states that SObjects can be returned by an InvocableMethod. I've writted a test class against the InvocableMethod that validates the returned object, and the test passes. I've also successfully returned strings into the flow.
I've searched known issues and the boards and not found anything related. Can anyone help?
When retrieving profiles for custom objects in a project.xml manifest, the returned profiles do not contain the objectPermissions object for objects that they do not have access to (ie no CRUD permission).
Steps to reproduce: Open a force.com developer edition instance Create an object named Object__c. Create a profile named Profile without any access to Object__c. Retrieve from metadata API (v.28 / eclipse) using the following package.xml
See that the profile received is as follows: <?xml version="1.0" encoding="UTF-8"?> <Profile xmlns="http://soap.sforce.com/2006/04/metadata"> <userLicense>Salesforce</userLicense> </Profile>
Before the Winter 14 upgrade, the profile contained: <?xml version="1.0" encoding="UTF-8"?> <Profile xmlns="http://soap.sforce.com/2006/04/metadata"> <objectPermissions> <allowCreate>false</allowCreate> <allowDelete>false</allowDelete> <allowEdit>false</allowEdit> <allowRead>false</allowRead> <modifyAllRecords>false</modifyAllRecords> <object>Object__c</object> <viewAllRecords>false</viewAllRecords> </objectPermissions> <userLicense>Salesforce</userLicense> </Profile>
Enable read access to the Object__c object for Profile.
Refresh from server, and see that the profile now contains: <?xml version="1.0" encoding="UTF-8"?> <Profile xmlns="http://soap.sforce.com/2006/04/metadata"> <objectPermissions> <allowCreate>false</allowCreate> <allowDelete>false</allowDelete> <allowEdit>false</allowEdit> <allowRead>true</allowRead> <modifyAllRecords>false</modifyAllRecords> <object>Object__c</object> <viewAllRecords>false</viewAllRecords> </objectPermissions> <userLicense>Salesforce</userLicense> </Profile>
We can see that the objectPermissions tag for that object is not retrieved in this profile when the profile has no access to the object.
Has anyone else encountered this issue, and found a workaround? This is causing issues for us, because if we remove object access from a profile, it will not be available to commit to our source control, and will not be updated when we deploy metadata to another enviornment.
I have methods currently working in salesforce which accept 0 and 2 or more arguments. The obvious way of calling these to me would be to simply include the arguments separated by commas as that is what is done with the current calls, e.g.
But for these two cases I get the following logged to the JS console:
Visualforce Remoting: Parameter length does not match remote action parameters: expected 0 parameters, got
Visualforce Remoting: Parameter length does not match remote action parameters: expected 2 parameters, got
So it is clear that salesforce know what it is expecting, but it is not clear how I pass the arguments.
I have also attempted passing the arguments as an array ,e.g.
[]
['1 argument']
['2','arguments']
and (in desparation) as a single object with the argument names as the parameter names! None of this works.
I have methods currently working in salesforce which accept 0 and 2 or more arguments. The obvious way of calling these to me would be to simply include the arguments separated by commas as that is what is done with the current calls, e.g.
But for these two cases I get the following logged to the JS console:
Visualforce Remoting: Parameter length does not match remote action parameters: expected 0 parameters, got
Visualforce Remoting: Parameter length does not match remote action parameters: expected 2 parameters, got
So it is clear that salesforce know what it is expecting, but it is not clear how I pass the arguments.
I have also attempted passing the arguments as an array ,e.g.
[]
['1 argument']
['2','arguments']
and (in desparation) as a single object with the argument names as the parameter names! None of this works.
