In a Flow I have a Decision Element with condition logic like so:
Opportunity.Date_Field__c is null GlobalConstant.TRUE
Opportunity.Date_Field__c greater than Custom_Object__c.DateField__c
with "One condition must be true (OR)"
I would expect that this would short-circuit after the first condition but I'm getting this error when my Flow runs:
The flow failed to access the value for Opportunity.Date_Field__c because it hasn't been set or assigned.
Do I need to separate this logic or is this a bug?
So I changed my Decision Element to have the first condition be in one outcome, and the second condition in a second outcome and I'm still getting the error.
After checking my logs, the Opportunity is getting assigned, but the Date_Field__c
doesn't seem to show up.
{
AccountId=0011800000QaheKAAR
CloseDate=2016-05-01 00:00:00
ContactId=0031800000LZHYjAAP
CreatedById=005C0000008cyo4IAA
CreatedDate=2016-08-16 14:05:27
ForecastCategory=Forecast
ForecastCategoryName=Commit
HasOpenActivity=false
HasOpportunityLineItem=false
HasOverdueTask=false
Id=00618000004L1yzAAC
IsClosed=false
IsDeleted=false
IsPrivate=false
IsWon=false
LastModifiedById=005C0000008cyo4IAA
LastModifiedDate=2016-09-30 13:10:11
LastStageChangeDate=2016-09-30 13:10:11
Name=Test1 - 2016-07-15
OwnerId=00580000003Xfe9AAC
Probability=100
RecordTypeId=012180000008id2AAA
StageName=Established
StageSortOrder=19
SystemModstamp=2016-09-30 13:10:11
}
{!Opportunity.Date_Field__c}
. Is this not enough, what would be the best way to reference it?