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

AudienceView 6.4.0 Fixes

Table of Contents | Previous

Desktop Fixes

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.4.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
Cannot filter gift searches by the fund's 'GL Code' when creating a link to a gift. This has been corrected in AudienceView 6.4.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
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.4.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.4.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
Payments are being rejected when an address' apartment and building numbers are both included on address line 1. This has been corrected in AudienceView 6.4.0.
Addresses are being verified when apartment and building numbers are both included on address line 1, and payments are being processed.		 AVT-6476
You cannot create an order with a Mail delivery method type when the customer account does not have a 'Country' or 'State/Province' indicated, even if the fields are not required fields. This has been corrected in AudienceView 6.4.0.
AudienceView now only requires that the 'Street Address' field be filled out instead of requiring all of the address fields.		 AVT-6423
AVT-6530
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.4.0.
Miscellaneous items do not need to have 'Options' to be sold via a bundle.		 AVT-6632
When an order containing a gift certificate that used the Email delivery method is updated, the gift certificate's 'Redemption Number' changes. This has been corrected in AudienceView 6.4.0.
The 'Redemption Number' of a gift certificate on an order that used the Email delivery method will not alter when the order is updated (unless the order is reprint).		 AVT-6664
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.4.0.
The included charges on a Drawdown bundle are being calculated properly.		 AVT-6818
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.4.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.4.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.4.0.
Scheduled payments on a saved/loaded order can be updated.		 AVT-6935
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.4.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.4.0.
The incorrect error message does not appear, and the user can update the order.		 AVT-7015
Seats are being displayed as Unavailable on the Customer Services application Seat|Map page when they are actually sold because the price/price zone is not available to the currently used role. This has been corrected in AudienceView 6.4.0.
Sold seats are now being shown in Customer Services application Seat|Map page even if the price/price zone is not configured for the currently used role.		 AVT-7044
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.4.0.
The error message is no longer appearing.		 AVT-7066
The draw down destination pop-up only appears on the Customer Services application Order|Bundles|Bundles page.
When removing a Draw Down performance from an order a pop-up appears allowing the user to determine if the money will be returned to the order or to the bundle; however, this message is only appearing on the Customer Services application Order|Bundles|Bundles page.		 This has been corrected in AudienceView 6.4.0.
The pop-up message now appears on the Order|Bundles|Seats page as well.		 AVT-7170
Performances must be on-sale on the Venue Configuration application Performance|Calendar page before they appear for sale within a bundle. This has been corrected in AudienceView 6.4.0.
As long as the performance is not explicitly off-sale, the Product Configuration application Bundles|Calendar page will override the Venue Configuration application Performance|Calendar page.		 AVT-7339
When Not Applicable is selected from the Application Security application Roles|Basic page, users receive the Message# 5656: The Address State is not Allowed by Role message when they attempt to create a customer account via the Customer Services application. This has been corrected in AudienceView 6.4.0.
Customer accounts can be created by roles that have Not Applicable selected from the Application Security application Roles|Basic page's 'Allowed Address States' field.		 AVT-7359
Deadlocks occur when adding/removing admissions to a performance via the Venue Configuration application. This has been corrected in AudienceView 6.4.0.
The deadlocks no longer occur when adding/removing admissions to a performance.		 AVT-7455
AVT-7457

Onlines Fixes

Issue Solution ID
If a default landing page is not defined on a site, AudienceView Online will not load and a JScript error will be displayed. This has been corrected in AudienceView 6.4.0.
If a site is created without a 'Default Article' set on the Content Management application Sites|Basic page (prior to AudienceView 6.2) or the Sites|Branding page (after AudienceView 6.2), the site will still load with the configured menu items (Sites|Menu Items page), the 'Page Header' and the 'Page Footer' articles (Sites|Basic page).		 AVT-1455
A 500 error occurs after selecting seats and then a delivery method on the oderContact.asp page. This has been corrected in AudienceView 6.4.0.
The error was being caused by empty 'Default Address Fields' and 'Default Contact Fields' values in the Registry. Null values no longer cause this error.		 AVT-6526
AVT-6535
AVT-6559
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.4.0.
A sold out message appears when users access a sold out performance via a deep link.		 AVT-6842
Payment methods are being displayed using the 'Labels' followed by the 'Name' in parentheseson on the AudienceView Online orderContact.asp page.
This is standard practice in the Desktop where disambiguation is required; however, this is not desirable in AudienceView Online and in instances when no disambiguation is required.		 This has been corrected in AudienceView 6.4.0.
The payment method 'Labels' are being displayed in AudienceView Online without the 'Names'.		 AVT-7201
When you attempt to check the balance of a gift card, a 500 error occurs in the pop-up. This has been corrected in AudienceView 6.4.0.
Gift card balances can be checked.		 AVT-7278
The payment installment option does not hold payment preference when data validation fails.
When a customer selects the payment installment option, and there is an error in the data entry (e.g. incorrect credit card data), the application displays an error message, and at the same time switches the payment option back to Pay in Full. This switch might go unnoticed, and once all information is corrected and submitted, the credit card is charged with the entire order balance amount, which is not expected by the customers.		 This has been corrected in AudienceView 6.4.0.
If an error occurs while completing a payment intstallment plan, the option remains selected.		 AVT-7282
When a large number of performances are on-sale, AudienceView Online hits an SQL limitation. This has been corrected in AudienceView 6.4.0. AVT-7388

Business Intelligence and Reports Fixes

Issue Solution ID
When here are gangways (entrances) in the middle of rows, and AudienceView has been configured so that the sections of seats on either side of the gangways are different (to prevent Best Available from assigning seats on both sides of the aisleway), the Hold Type Range report displays the rows with the incorrect number of seats on hold. This has been corrected in AudienceView 6.4.0.
The Hold Type Range report displays the correct number of seats on hold per row.		 AVT-3449
AVT-7434
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.4.0.
The Performance Settlement report now uses the same horizontal price zone ordering for the Unsold Admissions and the Sold Admissions sections.		 AVT-4783
The Hourly Ticket Sales report displays NaN in unexpected places. This has been corrected in AudienceView 6.4.0.
The Hourly Ticket Sales report no longer displays NaN.		 AVT-4895
AVT-6619
Comps appear to be causing Reporting anomalies.
Ticket Sales by Performance report is not reporting returns when the report is executed without date constraints.		 This has been corrected in AudienceView 6.4.0.
The Ticket Sales by Performance report is reporting returns correctly.		 AVT-5275
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.4.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.4.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
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.4.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
Running the AV Transaction report using the same 'Contract Date' from year-to-year is modifying the 'Start Contract Date' by one day. This has been corrected in AudienceView 6.4.0.
The 'Start Contract Date' is not being changed when the AV Transaction report is being run from year-to-year.		 AVT-6685
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.4.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.4.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
A number of miscellaneous item criteria is missing from the Customer object. This has been corrected in AudienceView 6.4.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.4.0.
All rows are being decrypted when appropriate.		 AVT-6955
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.4.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.4.0.
The LOG macro changed to LOG1.		 AVT-7056
The Donor Biography report is running for multiple customers.
When the Donor Biography report is run via the Customer Services application Customer|Basic page it returns results for all customers from the selected customer to the most recently created customer. It should only generate results for the one selected customer.		 This has been corrected in AudienceView 6.4.0.
When the Donor Biography report is run from the Customer Services application Customer|Basic page it is only returning results for the currently selected customer.		 AVT-7213
The 'Street' and 'City' fields are not available under the TSvenueCO. This has been corrected in AudienceView 6.4.0.
All of the address-related fields have been exposed in the Registry application Registry::EN::Collection Object::TSvenueCO::Field node.		 AVT-7317

Payment Fixes

Issue Solution ID
The 'Renewal Payment Method' field value is being reapplied to orders.
When the 'Renewal Payment Method' is removed from an existing order, the original selection still appears once 'Apply' has been clicked.		 This has been corrected in AudienceView 6.4.0.
The 'Renewal Payment Method' field remains blank once the original selection has been removed and the order is saved.		 AVT-7182

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.4.0.
The 'Admissions Total' (the grand total) and 'Admission Net' (the net total) are printing on ticket templates.		 AVT-505

Dataloader Fixes

Issue Solution ID
The dataloader is not operating through the command prompt command line. This has been corrected in AudienceView 6.4.0.
Dataloader jobs can successfully be run through the command prompt.		 AVT-6534
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.4.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.4.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.4.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

Database Fixes

Issue Solution ID
The draw down destination selection to order is not working after the bundle is renewed through an offer.
When an admission is released from a bundle order (renewed via an offer) and Order is selected from the draw down destination pop-up, the money remains on the bundle instead of the order.		 This has been corrected in AudienceView 6.4.0.
When an admission is removed from a draw down bundle, the money is moved to the selected destination.		 AVT-7168
Bulk emails are failing when the 'remoteSMTP' option is used when mail server responses exceed the 256-character column width in the database. This has been corrected in AudienceView 6.4.0.
Failed record responses are being truncated to 255 character.		 AVT-7266

AVTiki Fixes

Issue Solution ID
All alert pop-ups cause the screen to grey out, preventing customers from completing order. This affects both AVTiki and AudienceView Mobile.
On the final step of the order creation, the entire page is greyed out and none of the buttons on the page can be clicked; therefore, the reservation codes cannot be sent to friends.		 This has been corrected in AudienceView 6.4.0.
closeButton text has been added to AVTiki and AudienceView Mobile, allowing customers to close the pop-ups and continue through the order/reservation process.		 AVT-7202