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
- 309 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
Using Control-AddIn WebPageViewer in NAV 2016
Lilithyan
Member Posts: 32
Hello all,
got a Problem with a Control-AddIn that has me rather baffled. In NAV 2017 you have a new one called WebPageViewer. NAV uses this to give you a preview show (in page 9700, Email Dialog) of the email body if you defined a word document to be a Body for a report. When selected in NAV 2017 the AddIn created 4 Events.
ControlAddInReady(callbackUrl : Text)
DocumentReady()
Callback(data : Text)
Refresh(CallbackUrl : Text)
So I'd really like to use the AddIn in NAV 2016. I've taken the Folder WebPageViewer from the NAV 2017 Service Add-ins, copied it to the NAV 2016 NAV Service Add-ins, added the AddIn into the Control Add-ins Page and imported the zip-Folder. The Service has also been stopped and started a few times.
But when then selecting the Control-AddIn, NAV will not create the above mentioned events. And if I just Export the page 9700 from NAV 2017 and Import it into NAV 2016 I get the compiling error that the type cannot be loaded.
Any ideas what I'm missing or duing wrong? Would perhaps the PublicKeyToken be different from NAV 2016 to NAV 2017? Or is the whole Thing just not compatible with NAV 2016?
Ciao,
Lils
got a Problem with a Control-AddIn that has me rather baffled. In NAV 2017 you have a new one called WebPageViewer. NAV uses this to give you a preview show (in page 9700, Email Dialog) of the email body if you defined a word document to be a Body for a report. When selected in NAV 2017 the AddIn created 4 Events.
ControlAddInReady(callbackUrl : Text)
DocumentReady()
Callback(data : Text)
Refresh(CallbackUrl : Text)
So I'd really like to use the AddIn in NAV 2016. I've taken the Folder WebPageViewer from the NAV 2017 Service Add-ins, copied it to the NAV 2016 NAV Service Add-ins, added the AddIn into the Control Add-ins Page and imported the zip-Folder. The Service has also been stopped and started a few times.
But when then selecting the Control-AddIn, NAV will not create the above mentioned events. And if I just Export the page 9700 from NAV 2017 and Import it into NAV 2016 I get the compiling error that the type cannot be loaded.
Any ideas what I'm missing or duing wrong? Would perhaps the PublicKeyToken be different from NAV 2016 to NAV 2017? Or is the whole Thing just not compatible with NAV 2016?
Ciao,
Lils
0
Comments