Expand my Community achievements bar.

SOLVED

Help in migrating from adobe forms 6.0 to 7.1

Avatar

Level 2

Hi

I have a set of adobe templates that have been developed in Adobe Livecycle designer version 6.0.

Now I will have to move these to Adobe LiveCycleDesigner 7.1

I could get a document 'Compatibility of Adobe Designer 6.0 for designs with Adobe LiveCycle Designer 7.1"

I read abt the text formatting compatibility and event model compatibility of the form designs.

What could be the best way to do this?

If i open the version 6.0 in Adobe LiveCycle Designer 7.1 and do a simple "save-as"...will it work??

Appreciate your response

Thank you

1 Accepted Solution

Avatar

Correct answer by
Former Community Member

It is not the Designer per se that decides what is supported in your template ...it is the target version that you are designing to. So when you open it in Designer 7.1 then go into Form Properties/Defaults you will be given additional options for the target version. If you target version 7 then you can test the things that you mentioned .....if it causes you issues then you can change the target version to 6 and all should be the same as before.

Paul

View solution in original post

1 Reply

Avatar

Correct answer by
Former Community Member

It is not the Designer per se that decides what is supported in your template ...it is the target version that you are designing to. So when you open it in Designer 7.1 then go into Form Properties/Defaults you will be given additional options for the target version. If you target version 7 then you can test the things that you mentioned .....if it causes you issues then you can change the target version to 6 and all should be the same as before.

Paul

The following has evaluated to null or missing: ==> liqladmin("SELECT id, value FROM metrics WHERE id = 'net_accepted_solutions' and user.id = '${acceptedAnswer.author.id}'").data.items [in template "analytics-container" at line 83, column 41] ---- Tip: It's the step after the last dot that caused this error, not those before it. ---- Tip: If the failing expression is known to be legally refer to something that's sometimes null or missing, either specify a default value like myOptionalVar!myDefault, or use <#if myOptionalVar??>when-present<#else>when-missing. (These only cover the last step of the expression; to cover the whole expression, use parenthesis: (myOptionalVar.foo)!myDefault, (myOptionalVar.foo)?? ---- ---- FTL stack trace ("~" means nesting-related): - Failed at: #assign answerAuthorNetSolutions = li... [in template "analytics-container" at line 83, column 5] ----