Hello all,
we had the (mis-)fortune, that one of our customers took a look at the NAV 2017 Demo and saw the functionality to define an email Body via the Report Selection and the Custom Report Selection. The reaction of course was "Hey, this is cool! We want this in our database, too!".
But...! The customer has a NAV 2016 database (CU4) and currently doesn't want to upgrade to NAV 2017 for one functionality. So they asked us, if it were possible to replacate/copy the one from NAV 2017.
So far, it doesn't seem possible to me, as the the whole functionality is build upon the premiss that the email body is created as html (REPORT.SAVEASHTML). This sadly does not (!) work in NAV 2016 (they took it out cause... reasons?), but it is back in NAV 2017.
Bonusheadache: The whole thing uses new C/AL Functions called IMPORTSTREAMWITHURLACCESS and GETDOCUMENTURL.
Sooooo... is in your opinion any possiblity to make at least the html-functionality work in NAV 2016? Or would you recomend someting along the lines of Extended Text that then gets shoved into the email body?
Bonusquestion: Is it actually possible (like in the good ol' days of classic Client) to only (!) make a "technical" upgrade from NAV 2016 Client to NAV 2017 Client (without upgrading the objects)? Would/Could that be (part) of the solution?
Ciao,
Lils
we had the (mis-)fortune, that one of our customers took a look at the NAV 2017 Demo and saw the functionality to define an email Body via the Report Selection and the Custom Report Selection. The reaction of course was "Hey, this is cool! We want this in our database, too!".
But...! The customer has a NAV 2016 database (CU4) and currently doesn't want to upgrade to NAV 2017 for one functionality. So they asked us, if it were possible to replacate/copy the one from NAV 2017.
So far, it doesn't seem possible to me, as the the whole functionality is build upon the premiss that the email body is created as html (REPORT.SAVEASHTML). This sadly does not (!) work in NAV 2016 (they took it out cause... reasons?), but it is back in NAV 2017.
Bonusheadache: The whole thing uses new C/AL Functions called IMPORTSTREAMWITHURLACCESS and GETDOCUMENTURL.
Sooooo... is in your opinion any possiblity to make at least the html-functionality work in NAV 2016? Or would you recomend someting along the lines of Extended Text that then gets shoved into the email body?
Bonusquestion: Is it actually possible (like in the good ol' days of classic Client) to only (!) make a "technical" upgrade from NAV 2016 Client to NAV 2017 Client (without upgrading the objects)? Would/Could that be (part) of the solution?
Ciao,
Lils