Microsoft Dynamics 365 | Integration, Dataverse...

Custom MS Flow trigger suddenly stopped working

(0) Share

Report

Posted on by Pradip Raj

327

Hello,

MS Flow suddenly stoped working from 10th April, 2021.

Filtering condition : contains(tolower('subject'),'add') - IGNORE

Original row filter :

contains(tolower(subject),'add') and not(contains(tolower(subject),'address'))

We are checking that email subject contains Add keyword.

Error:

Exception parsing contains(tolower('subject'),'add') submitted for attribute filterexpression of callback registration. Target entity: email. Exception: System.InvalidOperationException: AttributeTypeCode not valid:PartyList
at Microsoft.Crm.ObjectModel.CallbackRegistrationTypeMapFactory.Get(AttributeMetadata attributeMetadata, EntityMetadata entityMetadata)
at Microsoft.Xrm.Sdk.Data.CodeGen.ClassTypeFactory.BuildType(String logicalName, IDictionary`2 entityMetadata, IDictionary`2 types, Boolean includeNonVirtualLogicalAttributes)
at Microsoft.Xrm.Sdk.Data.CodeGen.ClassTypeFactory.Create(IEnumerable`1 entityMetadata, Boolean includeNonVirtualLogicalAttributes)
at Microsoft.Crm.ObjectModel.EdmModelBuilder.BuildClrType()
at Microsoft.Crm.ObjectModel.EdmModelBuilder..ctor(EntityMetadata xrmMetadata, IOrganizationContext context, ILogger logger)
at Microsoft.Crm.ObjectModel.CallbackRegistrationEdmModelCacheItem.GetOrBuildEdmModel(Lazy`1 lazyXrmMetadata, String entitySetName, IOrganizationContext context, ILogger logger)
at Microsoft.Crm.ObjectModel.EdmModelEvaluator..ctor(IOrganizationContext context, Lazy`1 xrmMetadata, Entity entityData, String entitySetName)
at Microsoft.Crm.ObjectModel.CallbackRegistrationService.<>c__DisplayClass33_1.<ValidateInputEntity>b__1()
at System.Lazy`1.CreateValue()
at System.Lazy`1.LazyInitValue()
at Microsoft.Crm.ObjectModel.CallbackRegistrationService.ValidateInputEntity(IBusinessEntity entity, ExecutionContext context, IFeatureDetailContainer featureDetailContainer)

Anyone facing this issue?

I have the same question (0)

All responses (9)

Answers (0)

Suggested answer

LuHao 40,892 on at

Like (1)

Report

Hi Pradip,

It should be contains(tolower(subject),'add')

Quotation marks are not needed inside tolower().

Was this reply helpful? Yes No
Suggested answer

LuHao 40,892 on at

Like (0)

Report

In addition, you can use condition as the filter.

Was this reply helpful? Yes No
Pradip Raj 327 on at

Like (0)

Report

HI Lu Hao,

Thank you for your quick response. That was my bad.

I have corrected my post. My filter was same as you mentioned here but It was working fine previously. Suddenly stopped working these flows.

Thanks

Pradip

Was this reply helpful? Yes No
Pradip Raj 327 on at

Like (0)

Report

Yes, we can do this but I don't want to trigger the flows unnecessarily so that added row filter.

Thanks

Pradip

Was this reply helpful? Yes No
Suggested answer

LuHao 40,892 on at

Like (0)

Report

Hi Pradip,

Plesee change it to contains(tolower(subject),'add') and not contains(tolower(subject),'address')

not contains does not require parentheses.

Was this reply helpful? Yes No
Pradip Raj 327 on at

Like (0)

Report

Hi Lu Hao,

Thank you for the suggestion. I have tried your suggestion but still it's not working.

Error :

Exception parsing contains(tolower(subject),'add') and not contains(tolower(subject),'address') submitted for attribute filterexpression of callback registration. Target entity: email. Exception: System.InvalidOperationException: AttributeTypeCode not valid:PartyList

at Microsoft.Crm.ObjectModel.CallbackRegistrationTypeMapFactory.Get(AttributeMetadata attributeMetadata, EntityMetadata entityMetadata)

at Microsoft.Xrm.Sdk.Data.CodeGen.ClassTypeFactory.BuildType(String logicalName, IDictionary`2 entityMetadata, IDictionary`2 types, Boolean includeNonVirtualLogicalAttributes)

at Microsoft.Xrm.Sdk.Data.CodeGen.ClassTypeFactory.Create(IEnumerable`1 entityMetadata, Boolean includeNonVirtualLogicalAttributes)

at Microsoft.Crm.ObjectModel.EdmModelBuilder.BuildClrType()

at Microsoft.Crm.ObjectModel.EdmModelBuilder..ctor(EntityMetadata xrmMetadata, IOrganizationContext context, ILogger logger)

at Microsoft.Crm.ObjectModel.CallbackRegistrationEdmModelCacheItem.GetOrBuildEdmModel(Lazy`1 lazyXrmMetadata, String entitySetName, IOrganizationContext context, ILogger logger)

at Microsoft.Crm.ObjectModel.EdmModelEvaluator..ctor(IOrganizationContext context, Lazy`1 xrmMetadata, Entity entityData, String entitySetName)

at Microsoft.Crm.ObjectModel.CallbackRegistrationService.<>c__DisplayClass33_1.<ValidateInputEntity>b__1()

at System.Lazy`1.CreateValue()

at System.Lazy`1.LazyInitValue()

at Microsoft.Crm.ObjectModel.CallbackRegistrationService.ValidateInputEntity(IBusinessEntity entity, ExecutionContext context, IFeatureDetailContainer featureDetailContainer)

I don't think there is an issue with the syntax. There is something else was changed from Microsoft so that now this flow stopped working.

Was this reply helpful? Yes No
LuHao 40,892 on at

Like (0)

Report

Hi Pradip,

I was unable to reproduce it in my environment.

You can refer to this thread which is the same issue.

powerusers.microsoft.com/.../506304

And you can try this solution.

community.dynamics.com/.../build-efficient-flows-using-filter-expression-in-cds-current-environment-trigger

Was this reply helpful? Yes No
LuHao 40,892 on at

Like (1)

Report

First we can use compose to check the output of Subject field.

Was this reply helpful? Yes No
Suggested answer

Pradip Raj 327 on at

Like (0)

Report

Hi,

Issue:

Microsoft Product Group team have determined that the issue was callback registration was not occurring at the customer's end, likely due to them being created with an unsupported attribute type of Party List.

This was a known issue from our end and we are truly sorry for the inconvenience to you and your business.

This seems to have been caused by an issue with FCB in CDS/CRM.

Now it's working again after some fix from Microsoft. But still some flows are not working so I have turn off and turn on it again to fix the issue. But client's business affected due to this cause because there are some emails which were not converted to case. Still there is no workaround to create cases from old emails.

Was this reply helpful? Yes No