Report 360 Conversion
Report 360 Conversion
Embedded Files
This page contains useful tips and tricks when converting your old Report 360 templates to Reporter templates.
If you have been using the bundle called "Alterview Report 360 for NetSuite" (bundle ID 106006) Reporter offers some support for converting your old Report 360 Editor records into new Reporter Layout Builder records. If above mentioned bundle is installed in your account you will see the field called Based on Reporter360 Printout when creating a new Reporter Layout Builder record.
This field will list all your active Report 360 Editor records. If you want to convert an old Report 360, select the record as shown in above image. Assign your new record a Name and save.
Reporter will now automatically create Reporter Layout Builder record using the code from the selected record as well as all its datasets and searches. The Report 360 Data Collector custom record is the equivalent to the Reporter Dataset record. Most of the conversion works out of the box but there are some differences between Report 360 and Reporter. Below we list some of those changes. Please note that the above list is not necessarily exhaustive and there might be more differences.
This Reporter conversion tool helps you to do the majority of the conversion still.
Dataset filtering and dynamic Filter Value
Dataset filtering and dynamic Filter Value
One major difference between Reporter and Report 360 is how we use the Filter Value field on saved search to filter the search dynamically based on a field on our base record.
Reporter
In Reporter we define the base record as a dataset on its own and assign it a name, e.g. BaseRecord. When we want to reference a field as filter value from our base record we always need to reference our base record followed by the field.
For example: {BaseRecord.custrecord_my_custom_field}
If the value used for filtering is also a list/record type field Reporter would also require the inclusion of @id as Reporter would reference the textual value if that part is omitted.
For example: {BaseRecord.custrecord_my_custom_list_field@id}
Report 360
In Report 360 it is not required to reference the name of the base record data collector. All fields on the base record can be referenced based on their field id directly.
For example: {custrecord_my_custom_field}
Filter Field and Operator is entered in the same way for both solutions and do not require changes.
If the filter is based on the base records internal id we would also use {id} in both solutions. In other words, the base record doesn't have to be referenced in Reporter.
If the filter value is a static value, it is added in the same way also.
Check boxes and Currency/Numbers
Check boxes and Currency/Numbers
In Reporter, check box are returned as true boolean meaning that the value returned and available in the report would be either true or false depending on the value set on the check box.
For Report 360 however, the check boxes are returned as a string and either "T" or "F". That means that if you have logic in your report that needs to be updated to process the value correctly.
Reporter also returns currency and number fields as numbers and not as string while Report 360 sometimes treat them as strings. This could also potentially affect how your code runs initially when first creating your Reporter Layout Builder record based on an old Report 360 record.
Page updated
Report abuse