AudienceView Connect
 Product Guides   Knowledge Base   Discussions   Support   Annual Conference   Developer Guide Login   Developer Guides  
 
AudienceView Documentation

AudienceView 6.3.0 Fixes

Table of Contents | Previous

Desktop Sales Fixes

This section outlines fixes made to resolve issues found when performing day-to-day operations using AudienceView Desktop.

Issue Solution ID
If there are charge rows but no corresponding pricing rows, a warning message should appear.
If a price chart is created via the Venue Configuration application Price Charts pages, and a charge row has been configured on the Price Charts|Charges page, but nothing has been defined on the Price Charts|Pricing page no warning message is presented.		 This has been corrected in AudienceView 6.3.0.
If a price chart contains charges, but no pricing warning Message # 5597: There are currently charges associated with the price chart that do not have corresponding price rows. Continue? is displayed when 'Create' is clicked.		 AVT-2269
You are unable to add additional search fields in the Utilities application. This has been corrected in AudienceView 6.3.0.
The button has been added next to several fields throughout the application, allowing you to add additional fields to filter searches.		 AVT-2300
If a bundle element is removed, all of its versions should also be removed from Product Configuration application Bundle|Assignment page.
When a bundle element is removed from a bundle, the removed element's versions are still displaying in the 'Performances' column in the elements section of the Product Configuration application Bundle|Assignment page.		 This has been corrected in AudienceView 6.3.0.
Removed bundle elements no longer appear in the 'Performances' column in the elements section of the Product Configuration application Bundle|Assignment page.		 AVT-2509
After deleting an unused price chart, the user remains on the disabled (deleted) Price Chart|Basic page. Clicking the 'Create' button causes error Message # 4004: 1 validation error(s) occurred. This has been corrected in AudienceView 6.3.0.
The 'Create' button has been replaced with the 'Create New' button.		 AVT-2665
Cannot filter gift searches by the fund's 'GL Code' when creating a link to a gift. This has been corrected in AudienceView 6.3.0.
The 'Fund GL Code' field has been added to The Find Gifts Dialog Box. This field is available when creating links to gifts via the Correspondence application and Content Management application.		 AVT-2764
Entering duplicate values in the 'Keywords' field on the Venue Configuration application Performance|Basic causes a database error. This has been corrected in AudienceView 6.3.0.
If duplicate values are entered in the 'Keywords' field on the Venue Configuration application Performance|Basic, warning message 5418 appears indicating that a duplicate value has been entered.		 AVT-5201
The Seat Availability indicator does not appear in the Upsell/Add-on pop-ups when a search widget has been included. This has been corrected in AudienceView 6.3.0.
The ticket Availabiltiy property has been added to the Application Security application User|Content and Group|Content pages under Customer Services, allowing you to enable the ticket availability indicators.		 AVT-5589
The Customer Services application Seats|Calendar page duplicates the performance for each performance calendar row entry. This has been corrected in AudienceView 6.3.0.
The calendar no longer doubles the performance output.		 AVT-5814
When an admission is released after the tickets have been printed, the print count record for the admission increases by one. This has been corrected in AudienceView 6.3.0.
Cancelling/removing a printed ticket from an order does not increase the print count of the admission.		 AVT-6077
Updated renewal price types (for bundles) on the Customer Services application Order|Summary page are not reflected on the Order|Bundles|Seats page. This has been corrected in AudienceView 6.3.0.
Updated renewal price types (for bundles) on the Customer Services application Order|Summary page are reflected on the Order|Bundles|Seats page.		 AVT-6256
When Send Now is selected as the 'Schedule Option' on the Correspondence application Messages|Schedule page, messages are being delivered twice. This has been corrected in AudienceView 6.3.0.
Messages that are scheduled to be sent immediately are only being delivered once.		 AVT-6393
When using Internet Explorer 9, you cannot select any of the options available under the 'Options' menu on the AudienceView Desktop without using the keyboard short-cuts. This has been corrected in AudienceView 6.3.0.
Options listed under the 'Options' menu can be selected without using the keyboard short-cuts.		 AVT-6404
You are unable to configure the quantity of a miscellaneous items that appear in the 'Quantity' dropdown using AudienceView Online. This has been corrected in AudienceView 6.3.0.
The Registry application Registry::EN::Application::Online node's 'Max Items' field controls the number of miscellaneous items that can be purchased. This is set to 10 by default.		 AVT-6412
The 'Reprint' button labelling is misleading. The 'Reprint' button prints admissions that have not been printed, and also allows admissions to be printed using a delivery method other than the one originally used on the order. This has been corrected in AudienceView 6.3.0.
The 'Reprint' button has been renames 'ALT Print' because it actually uses a print method (which ever is selected) that is different from the one on the order.		 AVT-6467
The performance information is not being retained when users navigate away from the Customer Services application Seats|Map page.
After a performance has been loaded via the Customer Services application Seats|Search page, users are taken to the Seats|Map page. If users navigate away from the Seats|Map page when they return the performance information is no longer displayed on the Seats|Map, Seats|Availability and Seats|Quick Sales pages.		 This has been corrected in AudienceView 6.3.0.
Once loaded, the performance information will still be displayed on the Seats|Map, Seats|Availability and Seats|Quick Sales pages after users navigate away from and then return to the page.		 AVT-6511
Miscellaneous items require an option to be packaged as part of a bundle, even when the item does not require different options (e.g. a parking pass). When the bundle is added to an order, the miscellaneous item appears as Unavailable, the 'Quantity' field is read-only, and the 'Continue' buttons are greyed out This has been corrected in AudienceView 6.3.0.
Miscellaneous items do not need to have 'Options' to be sold via a bundle.		 AVT-6632
If existing customers make an online purchase from a secondary website (a venue that they do not have an 'Association' from), the 'Message Source' is not being updated and therefore the new 'Associaiton' is not being applied. This has been corrected in AudienceView 6.3.0.
'Message Sources' and 'Associations' are being applied to customers who are making first-time Online purchases from a particular venue/association.		 AVT-6803
Drawdown bundle charges are not being recalculated when the bundle is updated. The included service charge is remaining on the Drawdown performance, causing an error because the bundle value becomes $0.00 and the bundle is trying to retain the included service charge. This has been corrected in AudienceView 6.3.0.
The included charges on a Drawdown bundle are being calculated properly.		 AVT-6818
Cannot decrypt encrypted card numbers when extracting the information from a BI query. This has been corrected in AudienceView 6.3.0.
To decrypt encrypted card numbers via Business Intelligence, select the decrypt option from the Application Security application Group|Permissions page for applicable group's TSorderCO and TSorderPaymentCO properties.		 AVT-6819
Creating renewal orders via the Utilities application is causing the system to timeout. This has been corrected in AudienceView 6.3.0.
The 'AutoCommitFrequency' field in the Registry application System::Application node has been modified to also control the creation of renewal orders in addition to controlling the sending of email messages. During large batches of renewal order creations, the original large transaction will be auto-committed as specified by the 'AutoCommitFrequency' setting into smaller transactions to prevent the loss of renewal order records in the event of rollbacks. The default setting is 10. A 0 indicates that the Auto-Commit functionality has been disabled.
For more information, refer to Setting the Auto-Commit Frequency.		 AVT-6848
When multiple bundles with different service charges (all of which are configured with a Per Order 'Calculation' with a 'Cap' of 1) are added to an order, only one service charge is levied against the entire order. This has been corrected in AudienceView 6.3.0.
All of the applicable bundle charges are being applied to the order.		 AVT-6897
When purchasing a bundle containing a miscellaneous item that has a default value, the default value should be auto-populated when the customer is going through the purchase flow. This has been corrected in AudienceView 6.3.0.
AudienceView Online behaves in the same manner as the AudienceView Desktop so that the minimum quantity is auto-populated when a bundle containing a miscellaneous item that has a default value is purchased.		 AVT-6902
You cannot update a scheduled payment on an order that has been loaded via the Customer Services application Order|Search page. This has been corrected in AudienceView 6.3.0.
Scheduled payments on a saved/loaded order can be updated.		 AVT-6935
Merging customer records via the Customer Services application fails and produces a database error message. This has been corrected in AudienceView 6.3.0.
Merging customer accounts via the Customer Services application no longer causes the database error. The customer accounts are merged appropriately.		 AVT-6963
An error occurs when you attempt to change a customer's address or click the 'Add Address' button to add a new one an existing order. This has been corrected in AudienceView 6.3.0.
Customer address can be changed on existing orders.		 AVT-7002
When attempting to update an order containing a miscellaneous item that is not available to the role, the user is presented with an error message stating that the promotional code is invalid. This error message is unrelated to the actual error. This has been corrected in AudienceView 6.3.0.
The incorrect error message does not appear, and the user can update the order.		 AVT-7015
Quick Sales is not processing payments.
The Customer Services application Seats|Quick Sales page is displaying an error message when the 'Create Payment' button is clicked, indicating that a 'Payment Method' must be selected even if one has been.		 This has been corrected in AudienceView 6.3.0.
The error message is no longer appearing.		 AVT-7066

Online Fixes

Issue Solution ID
The 'Greeting Name' and 'Publish Name' fields are being populated differently depending on whether an account is created Online or via the Desktop.
  • When an account is created in the Desktop, the 'Greeting Name' and 'Publish Name' fields also display the information from the 'Title' field.
  • When an account is created In AudienceView Online, the 'Title' is not being added to the 'Greeting Name' and 'Publish Name' fields.
 This has been corrected in AudienceView 6.3.0.
The Online 'Greeting Name' and 'Publish Name' fields are being populated with any information included in the 'Title' field.		 AVT-530
Charts, bullet points and other formatting are not appearing in Internal messages that have been sent to customers' Message Centres. This has been corrected in AudienceView 6.3.0.
Formatting is now appearing in Internal messages that have been sent to customers' Message Centres.		 AVT-1275
When navigating away from the required change password page (changePassword.asp) a misleading pop-up message is displayed.
When users are on the required change password page (changePassword.asp) where users must change their passwords to continue with the order, and users click the 'My Basket' button, or any other link to add more items to their orders, users are navigated out of the changePassword.asp page. The following pop-up message displays: Attempting to load with invalid search criteria.		 This has been corrected in AudienceView 6.3.0.
If the password has expired, the user is taken to the change password page (changePassword.asp), where all of buttons/links are disabled. The user has two options:
  1. Change their passwords
  2. Click 'Cancel' and be effectively logged out
 AVT-4657
The obstructed view/accessibility message interferes with the add-on article pop-up.
When both an obstructed view/accessibility message and an add-on article have been configured against seat/performance, the performance pop-up appears over the add-on article pop-up. When the performance pop-up is closed, the add-on article pop-up also closes, preventing customers from selecting an add-on item.		 This has been corrected in AudienceView 6.3.0.
The add-on article appears first. Once an item has been selected or the pop-up has been closed, the obstructed view/accessibility message appears.		 AVT-5962
AVT-6643
You cannot add widgets to a newly created article via the Content Management application Article|Text page using Internet Explorer 8/9. This has been corrected in AudienceView 6.3.0.
Widgets can be inserted into an article using Internet Explorer 8/9.		 AVT-6040
Google Analytics' ecommerce tracking does not report when 3D-Secure is used. This has been corrected in AudienceView 6.3.0.
The Google Analytics reporting is correct when 3D-Secure is used.		 AVT-6590
If a user uses the browsers back button (Internet Explorer 8/9) after viewing an event's information article to return to the previously loaded search results, the 'Next Results Page' button returns the user to the same information article instead of a page of more search results. This has been corrected in AudienceView 6.3.0.
Customers can view the next page of search results.		 AVT-6616
An iDispatch error occurs when a customer attempts to create a duplicate account. This has been corrected in AudienceView 6.3.0.
The iDispatch error no longer occurs. Customers are still unable to create duplicate accounts.		 AVT-6671
When users attempt to purchase an offer using a credit card payment plan by selecting Installments under payment options, a message appears stating that the 'Payment Method' must have a value. This has been corrected in AudienceView 6.3.0.
Customers can purchase offers using a credit card payment plan.		 AVT-6762
If users mistype their credit card numbers while trying to create a renewal payment plan, an error message displays. After the message, the order adds the payment plan, but to multiple gift cards, and will not allow users to edit the information, add a credit card or add an additional payment. This has been corrected in AudienceView 6.3.0.
All scheduled payments are deleted if the payment fails (payments would fail if the credit card information is incorrect). The payment plan will be submitted the next time customers attempt to create the order.		 AVT-6763
When a user is directed to a sold out performance via a deep link there is no message indicating that the show is sold out. This has been corrected in AudienceView 6.3.0.
A sold out message appears when users access a sold out performance via a deep link.		 AVT-6842

Business Intelligence and Reports Fixes

Issue Solution ID
When a partially paid admission is being fully paid and then deleted, the net amount paid is being entered as the full amount instead of 0 as the paid_delta in the audit table. This has been corrected in AudienceView 6.3.0.
Payments are being allocated properly.		 AVT-2899
'Delivery Methods' pulled via the Gift object are displaying as GUIDs. This has been corrected in AudienceView 6.3.0.
'Delivery Methods' pulled via the Gift object are displaying delivery method names and not the GUIDs.		 AVT-4130
The Performance Settlement report sorts the 'Sold' and 'Unsold' price zone columns inconsistently. The Unsold Admissions section is sorting the 'Price Zone' column headers 'Value' and then by 'Hold Name'. This has been corrected in AudienceView 6.3.0.
The Performance Settlement report now uses the same horizontal price zone ordering for the Unsold Admissions and the Sold Admissions sections.		 AVT-4783
When performing a count using the Customer object promo code criteria with a 'Type' of has a value, nothing is being returned. This has been corrected in AudienceView 6.3.0.
Using the promotional code criteria through a Customer object returns the correct results.		 AVT-6265
The Order object does not contain all of the fields related to gifts. This has been corrected in AudienceView 6.3.0.
The following fields have been added to the Order object:
  • Gift ID
  • Gift Name
  • Gift Description
  • Gift Short Description
  • Gift Recommended Amount
  • Gift Recommended Value Type
  • Gift Marketing Data [1-8]
  • Gift Marketing Multi-Data [1-2]
 AVT-6351
Using 'Update Date' in a Gift BI query results in a database error and query fails to run. This has been corrected in AudienceView 6.3.0.
Gift BI queries execute properly when 'Update Date' is used.		 AVT-6421
The projected values in the Performance Availabiltiy report are incorrect when 'Include Open Holds' is set to Always. This has been corrected in AudienceView 6.3.0.
The projected values in the Performance Availability report are correct when 'Include Open Holds' is set to Always.		 AVT-6427
When a second order is creating using the 'New Order' option, the Forwarding Tickets is not in list for cancel_reason message appears, preventing the creation of the second order. This has been corrected in AudienceView 6.3.0.
When enabling the ticket forwarding functionality, ensure that a 'Default Value' is entered for the Order: Cancel Reason attribute on the Application Security application Group|Attribute page.
For more information, refer to Enabling Ticket Reprinting and Forwarding for the WebSales Group.		 AVT-6597
The AV Transaction report is displaying comp tickets twice, once in the top section with the regular admissions and once in the section where the comp ticket values are displayed. This has been corrected in AudienceView 6.3.0.
Comp tickets are only displaying once on the AV Transaction report.		 AVT-6698
The Price Chart Summary report is sorting by 'Label' instead of 'Value', which is inconsistent with other AudienceView reports. This has been corrected in AudienceView 6.3.0.
The Price Chart Summary report is sorting by 'Value'.		 AVT-6835
A 500 error occurs when a Bundle BI query that uses Order Renewal Section Name, Order Renewal Row or Order Renewal Seat as result members is run. The Business Intelligence|Preview page displays message Information Message #5528 There was an error executing a query. This has been corrected in AudienceView 6.3.0.
Bundle BI queries that use Order Renewal Section Name, Order Renewal Row or Order Renewal Seat as result members can be run successfully.		 AVT-6910
Changes to the 'Type' field on Business Intelligence|Criteria are not being applied. This has been corrected in AudienceView 6.3.0.
Changes to the 'Type' field on Business Intelligence|Criteria are being applied.		 AVT-6909
A number of miscellaneous item criteria is missing from the Customer object. This has been corrected in AudienceView 6.3.0.
The missing miscellaneous item criteria has been added to the Customer object.		 AVT-6921
The first row of extracted data remains encrypted after the data is extracted for the first time (and before accessing the Business Intelligence|Preview page). This has been corrected in AudienceView 6.3.0.
All rows are being decrypted when appropriate.		 AVT-6955
Running the Offer Status report using the 'Offer Name' criteria causes the system to crash/hang. This has been corrected in AudienceView 6.3.0.
When the report is executed it is now writing to the log file instead of the audit table. The Offer Status report runs without crashing the system.		 AVT-6967
If an Admission BI query is created using the 'Admission Acquisition Cost', 'Admission Amount 1' and 'Admission Amount 2' criteria, a 500 error occurs. This has been corrected in AudienceView 6.3.0.
The amount fields for 'Admission Acquisition Cost', 'Admission Amount 1' and 'Admission Amount 2' criteria in the database are now bigInt. The 500 error no longer occurs.		 AVT-7001
Incorrect LOG macro is being used.
The object name will not be pushed because LOG was used without any trailing number, which could potentially cause the application to crash.		 This has been corrected in AudienceView 6.3.0.
The LOG macro changed to LOG1.		 AVT-7056

Printing Fixes

Issue Solution ID
Values do not print when using 'Admissions Grand Total' and 'Admissions Net' on ticket templates. This has been corrected in AudienceView 6.3.0.
The 'Admissions Total' (the grand total) and 'Admission Net' (the net total) are printing on ticket templates.		 AVT-505
Users experience intermittent loss of printer settings while logged in.
When the security cache out is triggered and then there is changes to apply, the user related data is reloaded and in that flow, the location information is reset. This causes the printer/stock information to be removed and recreated, clearing any previous selections.		 This has been corrected in AudienceView 6.3.0.
Printers/stock selections are not being dropped when the security cache out is triggered.		 AVT-853

Dataloader Fixes

Issue Solution ID
The dataloader is not running jobs.
The Utilities application dataloader runs one job successfully after the AVScheduler service is initialized. Any job created after a successfully run job will not be completed because the dataloader batch log file is not being released after a job is run; therefore, the batch log file could not be opened for subsequent jobs.		 This has been corrected in AudienceView 6.3.0.
The dataloader batch log file is being closed and subsequent dataloader jobs are being run successfully.		 AVT-6918
Dataloader jobs are not appearing in the results. All Dataloader results (successes and failures) appear under the 'Number of Records Processed' column. This has been corrected in AudienceView 6.3.0.
An exception was being thrown if number of succeeded records were less than one. The 'Number Of Records Processed' column has been renamed to the 'Number Of Records Succeeded'. The 'Number of Records Failed' column has also been added. Dataloader jobs results are now more accurate and easier to read.		 AVT-6953
You are unable to distinguish between records that have been processed successfully or have failed.
The 'Number of Records Processed' column on the Utilities application Dataloader|Results page does not distinguish between successfully processed records and failures.		 This has been corrected in AudienceView 6.3.0.
The 'Number of Records Processed' column on the Utilities application Dataloader|Results page has been split into the 'Number of Records Succeeded' and 'Number of Records Failed' columns.		 AVT-6960

Common Fixes

Issue Solution ID
Creating renewal orders causes large amounts of memory to be used, similar to a memory leak. This has been corrected in AudienceView 6.3.0.
Large amounts of memory are no longer being used when creating order renewals.		 AVT-6578