AudienceView Connect
AudienceView Documentation

AudienceView 6.3.3 Fixes

Desktop Fixes

Issue Solution ID
There's a duplication of code around order charges calculations. It does not cause any errors in calculation and does not have any side effects. This has been corrected in AudienceView 6.3.3.
The duplicate code has been removed.
CORE-82
Hold that have been updated via the Customer Services application Seat|Map are not being updated properly in Venue Configuration application Performance Management|Holds page. This has been corrected in AudienceView 6.3.3.
Holds are being updated identically in both the Customer Services application Seat|Map and the Venue Configuration application Performance Management|Holds pages
MAINT-4
Deleting a bundle element from a previous sold bundle via the Product Configuration application causes a system error when any of the orders with the original bundle are loaded. This has been corrected in AudienceView 6.3.3.
Bundle elements cannot be deleted once a bundle containing the element has been sold. Instead a system error is returned and element is not deleted. Elements can be deleted if any sold items are first removed from orders.
MAINT-28
The General Configuration property in the Application Security appliation User|Content and Group|Content pages contains items that are not applicable to the General Configuration application. This has been corrected in AudienceView 6.3.3.
The following items have been removed from the General Configuration property:
  • Articles Basic
  • Articles Calendar
  • Articles Criteria
  • Articles Form Fields
  • Articles Select
  • Articles Text
  • Sites Branding
  • Sites Menu Items
  • Sites Select
MAINT-34
Additional, unrelated audit rows are appearing on the Customer Services application Order|History|Order and Order|History|Gifts pages when creating a gift order. This has been corrected in AudienceView 6.3.3.
The unrelated audit rows are no longer appearing on the Customer Services application Order|History|Order and Order|History|Gifts pages.
MAINT-35
An error occurs when a 'Ship-To' customer is added to an order that contains agent and customer accounts. This has been corrected in AudienceView 6.3.3.
The error no longer occurs.
MAINT-36
Adding ad hoc memberships via the Customer Services application Customer|Entitlements|Memberships page causes an error. This has been corrected in AudienceView 6.3.3.
Ad hoc memberships can be added to customer accounts.
MAINT-40
When 'Select All' is used on the Venue Configuration application Performance Management|Search page to make changes to the Price Zones (or Hold Types) of multiple performances, the changes are only being applied to the first performance. This has been corrected in AudienceView 6.3.3.
Changes that are made to price zones and hold types using 'Select All' on the Venue Configuration application Performance Management|Search page are being applied to all of the selected performances.
MAINT-49
MAINT-66
When sending a batch of emails, the record being inserted or updated in the AVScheduler is causing a not valid error. The error prevents the rest from being transmitted, and only one of the emails being is sent. This has been corrected in AudienceView 6.3.3.
The Registry application Registry::EN:: TScorrespondenceBO::Correspondence Details::Country and Registry::EN:: TScorrespondenceBO::Correspondence Details::State nodes' 'Unbound' attribute dropdown has been set to Yes, by default, so the validation error does not occur when the AVScheduler is trying to insert a 'Country' or 'State' value that is not on the list.
MAINT-143

Online Fixes

Issue Solution ID
Random authentication failures are being caused by invalid memory access. AudienceView Online users are periodically failing to authenticate, displaying a message that Online cannot proceed at this time or that the user cannot authenticate because the code is attempting to access a memory location after it has been freed. This has been corrected in AudienceView 6.3.3.
The authentication failures are no longer occuring.
AVT-8769
The AudienceView Online My Account offer count and customer notification does not appear if the offer was created using the Utilities application. Offers do appear when users select the offer tab of their on My Account. This has been corrected in AudienceView 6.3.3.
The offer count and customer notification appear in My Account when offers are created via the Utilities application.
MAINT-10
A donation of any kind 20 characters in length causes the system to hit an arithmatic overflow, creating a credit on the order that can be saved. This has been corrected in AudienceView 6.3.3.
By default, only a donation of 10 characters or less can be made. This amount is configurable via the Registry application Registy::EN::Business Objects::TSorderBO::Gifts::Pledge Date node 'Maximum Length' field.
MAINT-29
The alternative syntax used to suppress the "promo code accepted" pop-up when a the promotional code parameter is passed in on a URL is causing a tampering error.
The alternative syntax is promocode_access_code_url=[PROMO] as opposed to promocode_access_code=[PROMO].
This has been corrected in AudienceView 6.3.3.
Using the promocode_access_code_url=[PROMO] syntax when deep-linking to an item with a promotional code supresses the "promo code accepted" pop-up
MAINT-131
When using Internet Explorer 9, users have to scroll to find and use the 'Add To Basket' button on mapSelect.asp page. This has been corrected in AudienceView 6.3.3.
Scroll bars no longer appear when Internet Explorer 9 is set to 100% zoom.
MAINT-133
When the venue has multiple screens/sections and Show Seats is clicked, the seats are not being displayed. This has been corrected in AudienceView 6.3.3.
Both the seatResults.asp and showSeats.asp pages display seats for performances with multiple screen venue.
MAINT-140
Once seats have been added to the shopping cart using best available, the online user is unable to click Try Again to select alternative seats for that event. This has been corrected in AudienceView 6.3.3.
The Try Again link on the shoppingCart.asp page works, allowing customers to select alternative admissions for the selected performance.
MAINT-144

Business Intelligence and Reports Fixes

Issue Solution ID
Using 'First Word' results in a Saved Search BI causes error Message # 5517: Invalid result member in BI when a second search is performed. The search works if the search is reloaded. This has been corrected in AudienceView 6.3.3.
The error message no longer occurs and the search does not need to be reloaded.
MAINT-13
The Order Detail by User Role report returns unexpected results based on definition of the 'Order Date' criteria (This is the date the order was created). When admissions are removed from an order, the order no longer appears in the Order Detail by User Role report results. This has been corrected in AudienceView 6.3.3.
The Order Detail by User Role report returns all orders based on creation date.
MAINT-39
The End of Day Summary report runs for a long time. This has been corrected in AudienceView 6.3.3.
The End of Day Summary report returns results within one minute when the 'Sales Date Format' is set to Yesterday or a Date Range of two days. When 'Sales Date Format' is set to a Date Range of a month, the results are returned in less than two minutes.
MAINT-42
The Ticket Sales report is displaying the wrong price type and/or price type group.
A blank price type appears, but it contains a negative net value and negative count. These are refunds that should be part of an existing price type/group.
This has been corrected in AudienceView 6.3.3.
The Ticket Sales report is displaying the correct price types and price type groups
MAINT-80
Running the Wrap report using the 'Report On' dropdown's Price Type Group option, results in an 'ambiguous column name' error. This has been corrected in AudienceView 6.3.3.
The error no longer occurs when running the Wrap report.
MAINT-88
The Wrap report is displaying the wrong price type and/or price type group.
A blank price type appears, but it contains a negative net value and negative count. These are refunds that should be part of an existing price type/group.
This has been corrected in AudienceView 6.3.3.
The Wrap report is displaying the correct price types and price type groups
MAINT-92
Gift BIs are generating an incorrect SQL where clause when wildcards are used in 'Fund Names' and Does not equal is selected as the 'Condition'. This has been corrected in AudienceView 6.3.3.
The an incorrect SQL where clause is no longer occuring.
MAINT-98
The AV Transaction report 'Contract Date' is incorrect.
When a past 'Contract Start Date' is used as the criteria, the AV Transaction reports using the current year (e.g. running the report for the year beginning on January, 2012 will return results for the year beginning on January, 2013).
This has been corrected in AudienceView 6.3.3.
The AV Transaction report is generating results for the correct time period.
MAINT-115

Printing Fixes

Issue Solution ID
Issues have been reported when printing ticket template elements.
Signature cards are only printing some of the elements that were being printed in AudienceView 5.1. In some cases removing an element and replacing it has solved the issues, but not all.
This has been corrected in AudienceView 6.3.3.
All of the ticket template elements are printing as expected.
MAINT-71

Base Platform Fixes

Issue Solution ID
SMTP client crashes the application when trying to format a date for outgoing SMTP messages. This has been corrected in AudienceView 6.3.3.
The SMTP client has been updated so that the application no longer crashes when messages are timestamped.
AVT-8786
The readme.txt file should be removed from Online/ArticleMedia/Images/logos/ folder because it is flagged as a PCI vulnerability.
The file contains the following information:
* This folder is reserved for team or performance logos *
Logo images should be:
- transparent GIFs
- dimensions less than 70 x 70 pixels
This has been corrected in AudienceView 6.3.3.
The readme.txt file has been removed from Online/ArticleMedia/Images/logos/ folder.
MAINT-134

Dataloader Fixes

Issue Solution ID
An error occurs when a Dataloader source file of an Offer Details BI query contains a non-existent column and fails to load into the system. This has been corrected in AudienceView 6.3.3.
Offer Details BI query source files are being loaded by the Dataloader.
MAINT-1
The 'dataloaderjob_results_number_records' field is not required in ts_dataloader_job_results_audit table. This has been corrected in AudienceView 6.3.3.
The 'dataloaderjob_results_number_records' field has been removed from the ts_dataloader_job_results_audit table.
MAINT-124

WebAPI Fixes

Issue Solution ID
The WebAPI's dataloader.asp is not creating dataloader jobs and a 'filesNode' is null or not an object error is returned. This has been corrected in AudienceView 6.3.3.
The dataloader.asp was referencing some nodes that no longer exist. It is now referencing the appropriate nodes.
AVT-8998
The pageBuilder.asp should be removed from the UI/WebAPI folder. This has been corrected in AudienceView 6.3.3.
The pageBuilder.asp has been removed from the UI/WebAPI folder.
MAINT-132

AVTiki Fixes

Issue Solution ID
The AVTiki interface still uses the global.asa for Facebook application data (i.e. Facebook app ID, page ID and application secret). This has been corrected in AudienceView 6.3.3.
The AVTiki Facebook application data (i.e. Facebook app ID, page ID and application secret) is now configured
MAINT-102