Hi all,

I'm hoping for some attention from the Lightning team, but would appreciate any light anyone could shed on this.

We have a customer who has added a custom lookup field to the Opportunity object, pointing to Contact, with a lookup-filter criterion that permits only contacts related to the opportunity's parent account. The standard "new" page, when editing the custom relation, correctly shows a 2-item list containing one appropriate contact and a "new contact" item:


Meanwhile, we have a "new" Lightning override page that uses lightning:inputField inside a lightning:recordEditForm, and the relationship field doesn't seem to work correctly: it shows only a "recently used contacts" list that does not include the only Contact conforming to the lookup-filter criterion, and shows other ones instead:


If the user starts typing to find a contact and uses the "search" list item to activate the advanced search window, the list still shows only irrelevancies. Even if one of these incorrect records is selected, the user is prevented from saving the record because pre-save validation notices that the record violates the lookup-filter criterion:


In short, this really looks to us like a boolean-inversion bug in the code for the lists, presumably in an SOQL WHERE clause (or equivalent) that retrieves candidate contacts to populate it.

best regards,
Jim

Hi everyone and thanks in advance for reading.

We provide a managed package that needs access to the SOAP API from our server to perform CRUD operations on objects. We use the Salesforce user's session ID to authenticate, and our package is whitelisted through an API key so that everything works automatically in Group- and Professional-Edition orgs.

Our problem is that this approach doesn't work in other org types: a user lacking the explicit "API Enabled" setting cannot use our product in spite of the same API key that works just fine in Group/Professional.

This is a potential problem in a couple of our customers' community implementations, because our current best option (asking the customer to set "API Enabled" for the users concerned) would be bad practice. Can anyone advise on alternative approaches to support these users?

regards,
Jim

Hi all,

I'm hoping for some attention from the Lightning team, but would appreciate any light anyone could shed on this.

We have a customer who has added a custom lookup field to the Opportunity object, pointing to Contact, with a lookup-filter criterion that permits only contacts related to the opportunity's parent account. The standard "new" page, when editing the custom relation, correctly shows a 2-item list containing one appropriate contact and a "new contact" item:


Meanwhile, we have a "new" Lightning override page that uses lightning:inputField inside a lightning:recordEditForm, and the relationship field doesn't seem to work correctly: it shows only a "recently used contacts" list that does not include the only Contact conforming to the lookup-filter criterion, and shows other ones instead:


If the user starts typing to find a contact and uses the "search" list item to activate the advanced search window, the list still shows only irrelevancies. Even if one of these incorrect records is selected, the user is prevented from saving the record because pre-save validation notices that the record violates the lookup-filter criterion:


In short, this really looks to us like a boolean-inversion bug in the code for the lists, presumably in an SOQL WHERE clause (or equivalent) that retrieves candidate contacts to populate it.

best regards,
Jim

Hi everyone and thanks in advance for reading.

We provide a managed package that needs access to the SOAP API from our server to perform CRUD operations on objects. We use the Salesforce user's session ID to authenticate, and our package is whitelisted through an API key so that everything works automatically in Group- and Professional-Edition orgs.

Our problem is that this approach doesn't work in other org types: a user lacking the explicit "API Enabled" setting cannot use our product in spite of the same API key that works just fine in Group/Professional.

This is a potential problem in a couple of our customers' community implementations, because our current best option (asking the customer to set "API Enabled" for the users concerned) would be bad practice. Can anyone advise on alternative approaches to support these users?

regards,
Jim

Hi All,

  I was deleted some pages and classes from managed package, and made a version 3.0 and uploading to appexchange after security review. Now I need to be added those deleted components again to managed package because we couldn’t upgrade the app from lower version to latest version by missing components. It saying the error is

"Salesforce has blocked this package upgrade because the new package version removes some Apex code that one or more Visualforce pages or global Visualforce components need in order to function. Please contact your partner with this error information."

I have checked with the "View deleted components" tab in package there i can only see the components and no option to undelete from there.




And i have checked with recycle bin there i couldn't see my deleted components. 

Can any one guide me in dealing with this error.

Pls Urgent!

Thanks in advance!