Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Non-Window administrator logins will only be able to view reports and will not beable be able to make any changes to reports.

Note: It is benefiical beneficial to have some working knowledge/experience with Crystal Reports.

Important: Before making changes to Forms it is highly recommended that a backup of the orgininal original form/s be taken. 
See "Backup and Restore"


Accessing the Form Designer:

...

  1. Right click on a clear area of the form and select insert text object or to change the text in a text box, double click the box and edit the value.
  2. Exit the text box by clicking anywhere else in the form
  3. Click on the "Preview" tab to view any changes made.
  4. Click on the "Save Form" button to save these changes. 

 
design_text.png 


Important:

Updated on 2nd May 2016

Hi All,

I need to alert you all to a design change that is required in ALL EXISTING and NEW forms.

Historically we have used the PARAM_ fields to indicate form type modifiers when passing basic information from WMS to Crystal Reports.

Going forward we are looking to REMOVE or at least reduce these... so where possible DO NOT use or rely on PARAM fields.

For REPORTS this is not so much of an ISSUE - for FORMS (SALES, PICK, PACK etc) we will be REMOVING THE PARAM fields completely over the next 12 months.

Example: Typical Use of the {@PARAM_IsQuote}

if {@PARAM_IsQuote} = 1 then "QUOTATION" else
if {@BalanceDue}>0 and {SAL_Sales.SAL_TermsMessage}="Prepaid" then "PROFORMA INVOICE" else
if {PKL_PickList_Sale.PKL_Status}=-99 then "BACKORDER ADVICE" else
if {PKL_PickList_Sale.PKL_Status}=0 then "ORDER CONFIRMATION" else
"TAX INVOICE"

NEW FORMULA Suggestion:

if IIF,1,0) = 1 then "QUOTATION" else
if {@BalanceDue}>0 and {SAL_Sales.SAL_TermsMessage}="Prepaid" then "PROFORMA INVOICE" else
if {PKL_PickList_Sale.PKL_Status}=-99 then "BACKORDER ADVICE" else
if {PKL_PickList_Sale.PKL_Status}=0 then "ORDER CONFIRMATION" else
"TAX INVOICE"

Summary:

The main fields to be removed are: {@PARAM_IsReturn} {@PARAM_IsQuote} {@PARAM_ABN} {@PARAM_BarcodeField} {@PARAM_PKL_ID} (only used in manifest report)

Exceptions:
Multi Pick/Pack format will remain valid - however will be split to two separate RPT files in the future.

Use the following to replace: {@PARAM_IsReturn} with IIF,0,{SAL_Sales.SAL_IsReturn}) {@PARAM_IsQuote} with IIF,1,0) {@PARAM_ABN} no replacement - suggest hardcoding this on FORM as it does not change {@PARAM_BarcodeField} no replacement - as above - usually set during implementation - always use UDF1 {@PARAM_PKL_ID} (only used in manifest report) - use {PKL_PickLIst.PKL_ID}

Let me know if you have any questions...

This will only effect those customers that take up Cloud Services - which in time should be all customers - so in the meantime we can deal with updating forms on a case by case basis.

Regards,
Adam Wesley



Filter by label (Content by label)
showLabelsfalse
max5
spacesICXE
showSpacefalse
sortmodified
reversetrue
typepage
cqllabel in ("forms","customisation") and type = "page" and space = "ICXE"
labelscustomisation forms

...