This article will provide additional details on how Design Converter will behave with dynamic presentations.
Prerequisites
|
Design Converter and Dynamics
When utilizing Design Converter with presentations containing Dynamics, the following behaviors are to be expected:
- Dynamics (smart fields, form, or metadata) coming from the original presentation that should be converted will become static in the converted presentation:
- Any smart field present on the Normal view will become static – any smart field present on the Master view will not be ported over in the converted presentation as the slide Master/layouts from the destination template will be used.
- Dynamics created on the destination template will remain dynamic in the converted presentation:
- Any smart fields present in the Master view, form questions and metadata will be kept in the converted presentation.
- Any smart fields present in the Normal view will not be ported over in the converted presentation as the slide content originates from the original presentation to convert.
Generated presentation versus non-generated template
- A generated presentation, no matter if static or dynamic, has been downloaded/generated from the Templafy Library as an end-user.
- A non-generated template, no matter if static or dynamic, has been downloaded from the Admin Center as a tenant owner, tenant admin, or space owner.
Recommendations when using Design Converter
- If the presentation to convert (static or dynamic) is meant to be uploaded to the Library and distributed to end-users, a non-generated template must be used (otherwise a validation message will be displayed in the Admin Center upon upload “Presentation generated from Templafy”).
- If the presentation to convert isn't meant to be uploaded to the Library:
- Dynamic presentations with Updater enabled should be converted using a dynamic generated presentation.
WARNING: it should be noted that the dynamics will not automatically reflect the end-user's information, end-users will need to click "Update presentation" after the conversion to reflect their information. (John Doe generated the template initially and provided it to Jane Doe for conversion, any presentation converted using the template generated by John Doe will initially contain John Doe's information, however Jane Doe can click "Update presentation" after the conversion to update the information to hers). It should be noted that if Jane Doe sends the converted presentation to her colleague Jack Smith, Jack Smith will also be able to click “Update presentation” to reflect his information in the converted presentation. - Dynamic presentations without Updater enabled should be converted using a static non-generated template or a static generated presentation.
If a generated presentation is used for the conversion, it will not be updatable afterwards and will reflect the information from the user that originally generated the presentation. (John Doe generated the presentation initially and provided it to Jane Doe for conversion, any presentation converted using the presentation generated by John Doe will contain John Doe's information - not Jane Doe) - Static presentations should be converted using a static non-generated template or a static generated presentation.
- Dynamic presentations with Updater enabled should be converted using a dynamic generated presentation.
Comments
Article is closed for comments.