Expand my Community achievements bar.

Adobe Summit 2025: AEM Session Recordings Are Live! Missed a session or want to revisit your favorites? Watch the latest recordings now.

Mark Solution

This conversation has been locked due to inactivity. Please create a new post.

SOLVED

Size of Form

Avatar

Level 4

I have created a form in Livecycle designer and it has ended up being 1MB in size.  As it is being uplaoded to the web for client to completed, is there anyway of reducing the size of the document?

1 Accepted Solution

Avatar

Correct answer by
Former Community Member

Also you can control whether you embed the fonts or not. On the File/Form Properties/ Save Options make sure you turn off the Embed Fonts checkbox and the Accessibility Tags  check box. This means that the form will not be accessible and the fonts will have to be on the users system to be able to see the form the way you intend it....but it will be smaller.

Paul

View solution in original post

2 Replies

Avatar

Level 10

If you have a LiveCycle Server software installed, then by rendering the PDF will reduce the size drastically. But other wise, you need to consider the amount of fields you are using on the form and the fonts used in the form..

If you use MyriadPro, it will take less space.

Also under File -> Form Properties, under Save Options tab, remove the Embed Fonts checkbox, this may reduce size of the form.

Thanks

Srini

Avatar

Correct answer by
Former Community Member

Also you can control whether you embed the fonts or not. On the File/Form Properties/ Save Options make sure you turn off the Embed Fonts checkbox and the Accessibility Tags  check box. This means that the form will not be accessible and the fonts will have to be on the users system to be able to see the form the way you intend it....but it will be smaller.

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