Skip to main content
Question

Bad Metadata Error


Forum|alt.badge.img+4

We are receiving this error message from our environments.  We have done a Dictionary Cache Refresh but a deployment has not been done for 4 days.

 

Error stack:
Bad metadata error:
The group: CustomerOrderDeliveryGroup does not exist in dictionary!

 

We do our own deployments and develop in the Cust Layer just as FYI.  Did Refreshing the Dictionary Cache do something from our last deployment that caused this issue or how do these groups relate to the Dictionary

 

Thanks

5 replies

Thirunavukkarasu Kapilan
Hero (Partner)
Forum|alt.badge.img+10

Kusal Gunathilake
Do Gooder (Partner)
Forum|alt.badge.img+2

Hi @Thirunavukkarasu Kapilan / @DHPCALBRECHT ,
 

I am experiencing the same issue with the Purchase Order Authentication Rule Window.

Error stack:
Bad metadata error:
The list: PurchaseOrderAuthorizationRuleProjectCategory1List does not exist
in dictionary!


The projection cash and meta data cash have been cleared as per Kapilan's reply, but still the issue persists. 

Are there any workarounds you've found?

Best Regards,
Kusal Gunathilake


Forum|alt.badge.img+3
  • Do Gooder (Partner)
  • 7 replies
  • December 20, 2023

Hi, we experienced same issue when updating from 22R2 to 23R1.

The issue for us where that the “Solution Manager > Configuration > Page Configurations” was “Behind” in the “Base line Status” .
https://docs.ifs.com/techdocs/23r1/040_tailoring/225_configuration/200_client_configurations/400_rebase_configurations/


Forum|alt.badge.img+2
  • Do Gooder (Customer)
  • 4 replies
  • February 8, 2024

Hi, We experienced the same issue with “Purchase Order Authentication Rule” window and in our case it wasn’t customized or had any configurations. So we redeployed the projection and client files related to that page and refreshed projection/client/metadata/dictionary and security caches. It solved the issue.


Forum|alt.badge.img+6

I encountered the same error. In my case, the problem was on the “Page Configurations” page, which was “Behind” in the “Baseline Status”, just like @community-tor’s situation.

Performing a rebase for the page resolved the issue.

Thank you, @community-tor.

 

 

 

 


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings