Fluent Bug - False positive error when defining dictionary entries for cross-scope tables

Chris Yang
Tera Sage

yesterday

I'm encountering a Fluent validation error when creating dictionary entries in a scoped application for tables that exist in a different scope.

Issue: When I created a dictionary entry for the HRIT Operations Table (sn_hr_core_case_operations) within my scoped app (x_payp2_wd_cra), Fluent throws the following error:

 
'name' property should start with scope prefix 'x_payp2_wd_cra_' fluent (11)

Context:

  • The dictionary entry was auto-generated by a transform (not manually created)
  • The name property in sys_dictionary correctly references the target table name
  • This appears to be a false positive since the table belongs to a different scope (sn_hr_core)

Workaround: Adding the following comment above the problematic line allows the build to succeed:

// @fluent-ignore

Question: Is this expected behavior when extending tables from other scopes, or is this a bug in Fluent's validation logic? It seems the validator is incorrectly expecting cross-scope table references to use the current application's scope prefix.

Has anyone else encountered this issue or found a better solution than using @fluent-ignore?

0 Helpfuls
  • 157 Views
1 REPLY 1

Chris Yang
Tera Sage

yesterday

I figured out that you have to add "as any" after the table name if it's in a different scope. However I'd expect this to be automatically added as party of now-sdk transform.

0 Helpfuls