I ran into an issue where a VisualForce page containing custom style classes (in the head tag), and which displays fine in Classic, gets the custom classes supressed in Lightning. If raw styles are used (without classes), then those work.
Did anyone experience this and if yes then how can custom classes be used within VisualForce under Lighting?
I have encountered a strange issue. According to Salesforce official documentation with regards to restoring lookups on the target Salesforce organization once a record is shared I have the following setup:
Organization A
-------------------------------------
Object X
Lookup field 1
Formula field (Text), equal to the ID of the lookup record in Lookup field 1
Partner lookup ID (Text, length 100)
Organization B
-------------------------------------
Object X
Lookup field 1
Formula field (Text), equal to the ID of the lookup record in Lookup field 1
Partner lookup ID (Text, length 100)
The way the S2S subscribe / publish is setup is that Formula field from Org A is published into the Partner lookup ID text field on Org B and vice version. The reason for this is that lookup fields cannot be published / subscribed to via S2S. So a set of triggers use these auxilliary fields to derive the lookup value on the target organization. Now here is the strange behaviour:
When I forward a record from Org A to Org B the Partner lookup ID is correctly populated on Org B AND the proper lookup is set for the record on organization B, e.g. the trigger works fine, but on Org A the Partner lookup ID field is empty, although the formula field on Org B is populated. On receiving organization any changes are reflected immediately, but not the formula to text mapping from receiving organization to the source organization. When lookup is updated directly on Org B, it is immediatelly picked up by the formula field and only then it is reflected on Org A in the Partner lookup ID text field.
Let me know if you have an idea of what may be causing this. What I have tried:
1. Waited 15 minutes for the cache to refresh to reflect changes on the mapped field (according to SF documentation)
2. Tried sharing from Org A to Org B and vice versa, behaviour is one way, e.g. everything works when updates are done on the source org (, but changes to lookup ID are not reflected when done on target org (receiving org).
Experiencing a weird behaviour when using Salesforce to Salesforce. I have a set of triggers which programmatically auto-share Accounts, Opportunities, and other objects. All of the objects are auto-accepted without any problems, but not on all the objects the triggers fire on the receiving SF org. The setup is based on:
To re-link the parent object on the other end. For certain auto-forwarded objects the triggers on the other end do not fire, although the forwarded records are successfully created and automatically accepted, no insert triggers are triggered.
I would like to know if anyone had run into a need to programmatically accept a shared record ( via Salesforce to Salesforce ), avoiding the manual accept. Example of this is when I need to share an account with related opportunities, but opportunities have multiple lookups and are not auto accepted on the receiving org. I need to be able to auto-accept these programmatically and then re-map the lookups ( the re-mapping is a different matter which I am not concerned about ). The bottom line is: can records forwarded from a source org, which are not auto-accepted on target org, be programmatically accepted?
I ran into an issue where a VisualForce page containing custom style classes (in the head tag), and which displays fine in Classic, gets the custom classes supressed in Lightning. If raw styles are used (without classes), then those work.
Did anyone experience this and if yes then how can custom classes be used within VisualForce under Lighting?
Experiencing a weird behaviour when using Salesforce to Salesforce. I have a set of triggers which programmatically auto-share Accounts, Opportunities, and other objects. All of the objects are auto-accepted without any problems, but not on all the objects the triggers fire on the receiving SF org. The setup is based on:
To re-link the parent object on the other end. For certain auto-forwarded objects the triggers on the other end do not fire, although the forwarded records are successfully created and automatically accepted, no insert triggers are triggered.
I would like to know if anyone had run into a need to programmatically accept a shared record ( via Salesforce to Salesforce ), avoiding the manual accept. Example of this is when I need to share an account with related opportunities, but opportunities have multiple lookups and are not auto accepted on the receiving org. I need to be able to auto-accept these programmatically and then re-map the lookups ( the re-mapping is a different matter which I am not concerned about ). The bottom line is: can records forwarded from a source org, which are not auto-accepted on target org, be programmatically accepted?
