Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K 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
- 305 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 993 SQL General
- 384 SQL Performance
- 34 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
- 260 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Hyphen in Json vs. API PAGE BC13
sirvladd@hotmail.com
Member Posts: 1
Hi,
I'm trying to create a webhook to recieve events.
Json looks like this:
API Page like this:
detail-type properties:
Response from postman:
If I change the - (Hyphen) to _ (Underscore) in both Json and API page, it works perfectly.
Does anyone know if there is a way to use Hyphen, since this is not a Json I can control?
If I post the URL in a browser and login with basic auth I get this response.
"version":0,"id":"bc241211-1a88-1e71-1c54-891b28265225","detail_type":"","source":"","account":"","time":"0001-01-01T00:00:00Z","region":"","resources":""
Looks like the Odata parser has converted the Hyphen to Underscore.
I'm trying to create a webhook to recieve events.
Json looks like this:
API Page like this:
detail-type properties:
Response from postman:
If I change the - (Hyphen) to _ (Underscore) in both Json and API page, it works perfectly.
Does anyone know if there is a way to use Hyphen, since this is not a Json I can control?
If I post the URL in a browser and login with basic auth I get this response.
"version":0,"id":"bc241211-1a88-1e71-1c54-891b28265225","detail_type":"","source":"","account":"","time":"0001-01-01T00:00:00Z","region":"","resources":""
Looks like the Odata parser has converted the Hyphen to Underscore.
0