Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.5K Microsoft Dynamics NAV
- 18.5K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 264 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 992 SQL General
- 385 SQL Performance
- 33 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 259 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Options
Underscore character in the API page (extension)
Solmyr
Member Posts: 51
Dear all,
I need to create an API page with some fields with the underscore character (like "_id", etc.).
When publishing the extension I'm getting compiler Error AL0528: "The name of field controls in pages of the type API must be alphanumeric."
As a result, I can't publish my extension.
In my case the sender can not change the JSON structure, it's a payment provider who sends the same structure to other customers. I can only think of creating a proxy Azure Function which will receive the API call, format it, and forward it to the Business Central. Not a perfect solution due to multiple factors (security, transaction time, extra complexity, availability).
In the C/AL you can still create an API page and add a field with the underscore character, but it won't work in my case due to various reasons.
Do you maybe have any better idea of how to solve this issue?
It's BC 14, on-prem.
I need to create an API page with some fields with the underscore character (like "_id", etc.).
When publishing the extension I'm getting compiler Error AL0528: "The name of field controls in pages of the type API must be alphanumeric."
As a result, I can't publish my extension.
In my case the sender can not change the JSON structure, it's a payment provider who sends the same structure to other customers. I can only think of creating a proxy Azure Function which will receive the API call, format it, and forward it to the Business Central. Not a perfect solution due to multiple factors (security, transaction time, extra complexity, availability).
In the C/AL you can still create an API page and add a field with the underscore character, but it won't work in my case due to various reasons.
Do you maybe have any better idea of how to solve this issue?
It's BC 14, on-prem.
Oleg Dovgalenko
0