Expand my Community achievements bar.

SOLVED

Auto-numbering a print-only form

Avatar

Level 2

Greetings,

I am creating a form using LiveCycle Designer ES 8.2.  The form was created with the Purchase Order template within the program.  I want to add a field that will automatically assign a sequential number for tracking purposes.  This will be a print-only form and will not allow the user to save changes.  Is it possible for the form to "remember" each time it assigns a number and updating the field automatically with each use?

Thank you for your help,

Amanda Halvorson

1 Accepted Solution

Avatar

Correct answer by
Former Community Member

Amanda,

This cannot be accomplished without calling a server-side solution and persisting the form identifier. Each time the form is served to, or opened by, a user the form would have to call a server-side process (a JavaServlet, an ASPX/ASP.Net, or your technology of choice) to read and update the form identifier, whether it is stored in a database, a flat file, or XML.

Steve

View solution in original post

1 Reply

Avatar

Correct answer by
Former Community Member

Amanda,

This cannot be accomplished without calling a server-side solution and persisting the form identifier. Each time the form is served to, or opened by, a user the form would have to call a server-side process (a JavaServlet, an ASPX/ASP.Net, or your technology of choice) to read and update the form identifier, whether it is stored in a database, a flat file, or XML.

Steve

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] ----