function readOnly(count){ }
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
+ Start a Discussion
Hemanth BakthavatsaluHemanth Bakthavatsalu 

Workaround for case solution junction object

We are using standard case and solutions object which is used by the full license users.

However we have a custom case and  custom solution object, which is synchronized between the standard case and solution object using trigger on the standard case and solution..( custom case & solution object functionality was built for field tech's as we cannot afford the full license for every tech)

Challenge is synchronizing the standard case-solution junction object with custom case-solution junction object, as we cannot write a trigger on the junction object..(Is salesforce planning to introduce this functionality any time soon)

So we are planning to override the solution search page with vf page, in order to capture the select and delete of a solution on a case, should we override the "select" and " delete" links on the solution object..

Any other suggestions or solutions for this scenario...
John Dray 4John Dray 4
I feel your pain, the junction object is called CaseSolution, but there is only limited access to it. The other thing to bear in mind is that the Solution object is NOT being migrated to Lightning. (See the road map.) Salesforce are expecting this to be moved to Knowledge, which is available in Unlimited, Service Cloud or as a paid extra in Sales Cloud. This may affect how you want to proceed.