This content has been marked as final. Show 4 replies
It is possible, have a look in the knowledge base for Negative reporting or Combined analysis, one of these will fix your problem. What I usually do to avoid this is make Account and CO1 a required field which means it always has a value, and create 1 Account and 1 CO record that says Unknown so they can still attach a record if they don't know it.
this Inner join is a common issue, hope this helps.
The problem you are facing is quite common. This is a kind of limitation in CRMOD.
I have a solution for you, however, my assumption is that you would be using ONLY the Account Name or CO Name in the report and no additional fields from the Account and Object.
The solution would be to do the following:
1. Create Two Custom fields in Service Request level, one for the Account Name and the other for the CO Name.
2. When ever the SR is created please populate one SR custom field with the Account Name and the other SR Custom field with CO Name. You need to use the Post default in the two fields.
3. When ever the user changes the Account or the Custom Object please use workflows to update the custom fields at SR level.
4. Use the Custom fields instead of the system Account Name or CO Name in the report.
In Case there are Other Account Fields that need to appear in the report, kindly convice the users that this much is only feasible.