web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Finance forum / BP Rule: [BPErrorUnkno...
Finance forum

BP Rule: [BPErrorUnknownLabel] issue while using label in class in D365 FO 10.0.1 PU25

(0) ShareShare
ReportReport
Posted on by Kathiravan 215

Hi,

We created label file as FDL  and label as eg: @FDL9001.

while using in class I used as warning("@FDL:@FDL9001"). this takes as string.

if I use like warning(@FDL9001) this takes as label but shows the BPErrorUnknownLabel issue.

BPErrorUnknownLabel: BP Rule: [BPErrorUnknownLabel]:Path: Unknown label '@FDL9001'.  Legacy labels (such as the label id @SYS12345) are case insensitive and modern labels (such as 'MyLabelId' in @MyLabelFile:MyLabelId) are case sensitive. Use upper casing when referring to legacy labels and exact casing for modern labels.

when I refer this link https://community.dynamics.com/ax/f/33/t/253388.

here, they suggested to create without @ and use as @FDL:FDL9001 (in-case of new label).

For this also am getting the same error while running Run best practice fixers through solution explorer.

It looks little bit confusing whether to create label with @ and without @.

Note : if I build the package with Run best practice checks - checked I didn't get any error like this.

Please clarify this.

Thanks & Regards

Kathiravan M

Categories:
Development / Customization / SDK
I have the same question (0)
  • Martin Dráb Profile Picture
    Martin Dráb 237,882 Most Valuable Professional on at

    Sometimes the BP check get confused; I wouldn't take it too seriously if the functionality works. When I got a persistent problem with a label, I think I had to delete the resource file generated from the label file and let if generate again.

    In older versions of AX, label IDs had the pattern @[three letter ID][generated number], such as @XYZ12345. They're still there for backward compatibility, but now you should use the label file name + (hopefully) meaningful label ID. Therefore instead of @XYZ12345, you can use something like @AccountingModule:ParamFormCaption.

  • Kathiravan Profile Picture
    Kathiravan 215 on at

    Thanks Martin,

    As you mentioned if I am creating a label for example : Label file name as TEST and label as SampleLabel. I will use like @TEST:SampleLabel. No need to worry about @. we can create labels like SampleLabel instead of @SampleLabel.

    In case if the label file is migrated from AX 2012R3, those label looks like @XYZ12345. How to proceed further at this case?

    You mentioned as delete the resource file generated from the label file and let it generate again. how to generate it again?

  • Suggested answer
    PA-22040759-0 Profile Picture
    PA-22040759-0 6,194 on at

    Is I recall, if of you use the upgrade tools from LCS they'll remove the @ from your upgraded labels.

    For me a full build of the model typically fixes label problems similar to what you describe. The build will also regenerate the ressource files.

  • Gerd K. Profile Picture
    Gerd K. 5 on at

    You have to create your label in every language based label file you created in your model.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

November Spotlight Star - Khushbu Rajvi

Congratulations to a top community star!

Forum Structure Changes Coming on 11/8!

In our never-ending quest to help the Dynamics 365 Community members get answers faster …

Dynamics 365 Community Platform update – Oct 28

Welcome to the next edition of the Community Platform Update. This is a status …

Leaderboard > Finance

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans