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

AudienceView 6.7.0 Fixes

Table of Contents | Previous

Desktop Fixes

Issue Solution ID
When an order contains a miscellaneous item with a 'Type' of Other, service charges are not being applied after a delivery method is selected. This has been corrected in AudienceView 6.7.0.
The expected service charges are being added to orders that contain miscellaneous items with a 'Type' of Other.		 AVD-136
AVD-664
When an Agent customer account is on an order and you cannot convert the order to an offer using the 'Make Reservation' button on the Customer Services application Order|Summary page. This has been corrected in AudienceView 6.7.0.
Orders with Agent customer accounts can be converted to offers; however, the Agent customer number will be populated in the 'Customer Number' field instead of the 'Agent Customer Number' field on the Customer Services application Offer|Summary page.		 AVD-141
AVD-674
It is not possible to control the content of the Customer Services application Order|Order History|Charges page with the Order History: Charges nor with the Order History Order Service Charges content option available in the Application Security application. This has been corrected in AudienceView 6.7.0.
Deprecated Registry entries in the Registry::EN::Content Management node were not being updated when systems were migrated to newer versions of AudienceView. This is particularly true if a user/group was configured using the now deprecated values. New migration scripts will updated deprecated values.
The Customer Services application Order|Order History|Charges page is controlled by the Order History Order Charges option in the Application Security application Users|Content and Group|Content pages.		 AVD-609
AVD-2019
Drawdown bundles are not being recalculated properly when items on the bundle are refunded. This has been corrected in AudienceView 6.7.0.
Drawdown bundles are being recalculated properly when items are refunded.		 AVD-666
When searching for a gift card that has been purchased, used and then reloaded using the Customer Services application Gift Certs/Card|Search page, multiple rows of search results are returned. This has been corrected in AudienceView 6.7.0.
The Customer Services application Gift Certs/Card|Search page now returns one row of search results with the most current balance.		 AVD-781
An incorrect Correspondence Detail ID is generated when unsubscribe links are inserted into email messages. Instead of displaying the appropriate article, the error.asp page is displayed. This has been corrected in AudienceView 6.7.0.
Unsubscribe links are correctly generating the Correspondence Detail ID.		 AVD-804
When a data field or question has been configured so that 'Optional' is set to No, the --Select One-- text does not display. This has been corrected in AudienceView 6.7.0.
The --Select One-- text is displaying for data fields or questions when they have been configured so that 'Optional' is set to No.		 AVD-833
Changing the 'Delivery Method' or 'Payment Type' on a saved quick sale order (Customer Services application Order|Summary page) displays message 1242: The Business Object is in an invalid state and cannot be used: TSmapBO, preventing you from being able to update the order. This has been corrected in AudienceView 6.7.0.
You can update a saved quick sale order as expected.		 AVD-884
When the Registry application Registry::EN node's 'Locale' field is set to nl_NL, BOCA tickets are being printed with 0.00 instead of the actual price. This has been corrected in AudienceView 6.7.0.
BOCA tickets are being printed with the correct prices regardless of the locale.		 AVD-993

Online Fixes

Issue Solution ID
When customers create reservations for print-at-home tickets after their card was declined, they are receiving PDF tickets along with their reservation confirmations. This has been corrected in AudienceView 6.7.0.
Customers are no longer receiving PDF tickets with their reservation confirmations.		 AVD-142
The contact phone number appears on the logindelivery.asp page without labels or context. This has been corrected in AudienceView 6.7.0.
A label now appears identifying the phone number.		 AVD-669
Invoicing an offer through the Utilities application incorrectly increases the offer count on the offers tab in the customer's account. This has been corrected in AudienceView 6.7.0.
The appropriate number of offers are displayed on the offers tab in the customer's account after they are invoiced via the Utilities application.		 AVD-769
Switching between the Best Seat Available tab (seatSelect.asp) and the Select Your Own Seats tab (mapSelect.asp) causes the mapSelect.asp page to appear as a blank white page. This has been corrected in AudienceView 6.7.0.
You can now switch between the two tab freely.		 AVD-822
After entering a promotional code on the best available page, the validation pop-up does not display (although the code is accepted). This has been corrected in AudienceView 6.7.0.
A validation pop-up is appearing on the best available page when promotional codes are accepted.		 AVD-831
When customers select offers with future dates from within their accounts, they are redirected to the error.asp page and the following message is displayed: The Offer is not available to be added to the order. User has to start again/login. This has been corrected in AudienceView 6.7.0.
If the offer's 'Start Date' is in the future, Offer Available will appear with the 'Start Date' underneath it. On that date, customers will be able to accept/partially accept/decline the offer.
The Offer Available label can be configued using the Registry application Registry::EN::Online::Offers node 'Offer Available' field.		 AVD-882
When searching for a performance via the calendar widget, and then clicking the right arrow to navigate to the next month, a NAN error, the days of the week are in English (for multi-language installations) and the widget freezes. This has been corrected in AudienceView 6.7.0.
The calendar widget no longer displays the NAN error, and customers can navigate from month to month.		 AVD-951
When a default payment method has been set against the WebSales (e.g. Visa) group, the Payment Information section of the orderContact.asp page does not display unless 'Change Payment Method' is clicked. This has been corrected in AudienceView 6.7.0.
The Payment Information section of the orderContact.asp page displays automatically when a default payment method has been set against the WebSales group.		 AVD-976
When you zoom-out of a seat map using Chrome, the image shifts further into the top-left corner of the screen. This has been corrected in AudienceView 6.7.0.
The image no longer shifts.		 AVD-979
The payment method's 'Payment Name' is being displayed on the orderContacts.asp page instead of the 'Label'. This has been corrected in AudienceView 6.7.0.
The payment method's 'Label' is now being displayed on the orderContacts.asp page.		 AVD-983
If an apostrophe is added to one of the online fee messages (Registry::EN::::Application::Online::Seats::Fee Message [1-5] nodes), the pick-a-seat functionality breaks, the 'Full Map' button does not work and the pop-up messages stop working. This has been corrected in AudienceView 6.7.0.
You can now added apostrophes to the Registry::EN::::Application::Online::Seats::Fee Message [1-5] nodes without impacting the online functionality.		 AVD-1067
When online users recover their passwords, an incorrect password is generated that cannot be used to log-in. This has been corrected in AudienceView 6.7.0.
Online user users can use the Forgot Password link to reset their passwords. Customers can then use the temporary password that they receive to log-in.		 AVD-1282
When navigating directly to the login.asp page, users receive an Record not found error after they log in. This does not happen if users are linked to the login.asp page from the default.asp page. This has been corrected in AudienceView 6.7.0.
Users do not receive the Record not found error regardless of how they login: directly from the login.asp page, redirected via a link to the login.asp page or using the Login widget.		 AVD-1577

Business Intelligence and Reports Fixes

Issue Solution ID
When there is a space in a formula 'Name' (on the Business Intelligence|Formulas page) and that formula is one of the result members (on the Business Intelligence|Results page), you cannot email a PDF extract of the report. When the space is replaced with an underscore the PDF extract of the report can be emailed as expected. This has been corrected in AudienceView 6.7.0.
A formula 'Name' can now contain spaces and PDF extracts will be successfully emailed.		 AVD-137
AVD-683
Formulas that use the SUM function will not save nor will they extract to CSV. This has been corrected in AudienceView 6.7.0.
Formulas can now be saved and extracted to CSV when the SUM function is used.		 AVD-613
You are unable to report on customers who have used a promotional code via BI. This has been corrected in AudienceView 6.7.0.
The Promotion Code ID criteria has been added to the Customer BI.		 AVD-649
When the Ticket Sales by Price Type and Price Zone report is generated with the 'Group Price Types By' set to Price Description or Price Type Description and Price Type, the output columns do not appear in alphabetic/numerical order. This has been corrected in AudienceView 6.7.0.
The output columns appear in alphabetic/numerical order.		 AVD-772
The Unbalanced Order report no longer renders the order numbers as hyperlinks. This has been corrected in AudienceView 6.7.0.
The order numbers on the Unbalanced Order report, allowing you to easily navigate to orders.		 AVD-836
When the Ticket Sales by Price Type and Price Zone report is run for a series with default criteria, but 'Group Price Types By' dropdown is set to Price Type Group and Price Type the final group appears to get intersected by another group. Each part of the split has its own summary, with the totals in the second still calculating those from the first. This has been corrected in AudienceView 6.7.0.
The price types are no longer intersected by another price type group.		 AVD-886
The Gift Certificate/Card Transactions report shows the incorrect 'Purchased' and 'Balance' figures in regards to reloads. This has been corrected in AudienceView 6.7.0.
  • Reversal/Return of a Gift Card/Cert Reload: When a gift card is purchased or reloaded and then deleted from the order, the removal from the order is displayed as a negative number in the 'Purchase' column on the report, reversing the purchase/reload.
  • Reversal/Return of a Gift Card/Cert (not yet redeemed): When a gift certificate is purchased then deleted from the order, the removal from the order is displayed as a negative number in the 'Purchase' column on the report, reversing the purchase.
  • Reversal/Refund/Void of a Gift Certificate/Card payment: A redemption that is reversed, using the 'Void' or the 'Refund' buttons on the gift certificate/gift card payment, appears in the 'Redeemed' column as a negative number, reversing the redemption. The balance returned to the gift card/certificate displays in the 'Balance' column.
 AVD-912
AVD-1470
When the following criteria is used on the Wrap report, the incorrect formula is being used for the 'Projected Values':
  • 'Include Open Holds' dropdown set to Always
  • 'Output' set to Performance, Performance Description or Series
 This has been corrected in AudienceView 6.7.0.
The incorrect formula being used was: [Net amount from Total to date] + [(seats open)(performance model price)(capacity of venue minus holds)]
The corrected formula is now being used: [Net amount from Total to date] + [(seats open)*(performance model price)]		 AVD-1004
Reloading gift card transactions incorrectly persists the payment reference in the Gift Certificate/Card Transations report. For example:
  1. Purchase Gift Card A for $10.00 and Gift Card B for $20.00.
  2. Reload Gift Card A with $5.00.
  3. Pay $3.00 of an order with Gift Card B.
  4. Reload Gift Card B with $4.00.

    The reloaded amount of $5.00 on Gift Card A displays under the 'Purchased' column of the Gift Certificate/Card Transations report (as expected).
    The reloaded amount of $4.00 on Gift Card B displays under the 'Redeemed' column of the Gift Certificate/Card Transations report (not expected).
 This has been corrected in AudienceView 6.7.0.
Both of reloads are displayed under 'Purchased' column in Gift Certificate/Card Transactions report.		 AVD-1525
Sales Audit report is timing out. This has been corrected in AudienceView 6.7.0.
The Sales Audit report is now a Historical report rather than Current State. This means that if the report is generated for a specfic date/range, the results returned will be the same regardless of when the report is generated.
The unallocated amounts were being generated correctly.
The report is no longer timing out.		 AVD-1578
The Customer Payment Account Number criteria (when creating a Customer BI) is not masked by default. This has been corrected in AudienceView 6.7.0.
The Registry application Registry::EN::Collection Objects::TSCustomerCO::Fields::Customer Payment Account Number and Registry::EN::Collection Objects::TSCustomerCO::Fields::Card Number nodes now have the following default configuration:
  • The 'Mask' field is set to 0x -4o
  • The 'Masked' dropdown is set to Yes
 AVD-1607

AVTiki Fixes

Issue Solution ID
The Facebook API has dropped the support for 'Description', 'Picture' and 'Name' in the JavaScript send function. This has been corrected in AudienceView 6.7.0.
When sending a saved notice to a Facebook friend, the link now displays the following message <Performance Description> on <Venue Description> at <Performance Start Date>. The message used to also contain the location of the seats.
Some additional configuration is also required:
  1. In a web-browser, navigate to Facebook’s developer site https://developers.facebook.com/apps.
  2. Login using a developer account with admin rights on your organization's Facebook page.
  3. Click 'Edit App' (or 'Create New App' if you are creating a new AVTiki instance).
  4. Select Advanced from the left-hand panel under Settings.
  5. Ensure that 'Stream Post URL Security' is set to Disabled.
  6. Click 'Save Changes' at the bottom of the screen.
 AVD-1117

WebAPI Fixes

Issue Solution ID
Empty strings are returned as an empty array in JSON. This has been corrected in AudienceView 6.7.0.
An empty multi now return as an empty string. The following syntax should be used:
  • Non-multi, has a value: NAME:"VALUE"
  • Non-multi, null/empty: NAME:" "
  • Multi, null/empty: NAME:[ ]
  • Multi, single value: NAME:["VALUE"]
  • Multi, multiple values: NAME:["VALUE_1", "VALUE_2"]
 AVD-1104
An invalid BO handle will fall through to the default/unknown exception response (WebAPI result code 6). This deserves a dedicated result code and message. This has been corrected in AudienceView 6.7.0.
Status code 33 has been added to identify a business object that does not have a handle in the cache.		 AVD-1206
The error JSON response is inconsistent between the Java and ASP versions of the WebAPI. For example, the Java version outputs Error level whereas the ASP version outputs error. This has been corrected in AudienceView 6.7.0.
The error JSON response is now consistent between the Java and ASP versions of the WebAPI.		 AVD-1217
In the ASP WebAPI, it is possible to GET the primitive value, but not its DETAILS. This has been corrected in AudienceView 6.7.0.
The node search method for DETAILS differed from that used for GET.
DETAILS has been updated to utilize TSbusinessNode::findInTree(context) so that it is consistent with the other WebAPI GET and SET implementations.		 AVD-1218
The WARNING parameter does not suppress messages in ASP. This has been corrected in AudienceView 6.7.0.
The WARNING parameter has been renamed ACCEPTWARNING, and messages are being surpressed as expected.		 AVD-1224
The COM implementation is corrupting the api.asp result because the BSTR constructed and passed to the ASP is relying on a temporary variable that is freed mid-stream. This has been corrected in AudienceView 6.7.0.
The BSTR construction and handover to ASP has been corrected.		 AVD-1300
The article 'Page Size' overrides the user entered 'Page Size', and the TScontentBO pagination overrides the user entered 'Page Size' by always resetting to the Registry default when a search is executed. This has been corrected in AudienceView 6.7.0.
If a 'Page Size' has been defined in a WebAPI call, it will override tghe 'Page Size' setting in the article/Registry.		 AVD-1449
Site should be optional. This has been corrected in AudienceView 6.7.0.
Site is no longer required when initializing the site.		 AVD-1453
If branding has not been loaded then TScontentBO::search will not work and will throw branding related exceptions such as The site branding does not exist. TScontentBO::search should be able to run if branding is not loaded. The exception is thrown when TScontentBO::search tries to load the default search article. This problem prevents the WebAPI from running TScontentBO::search since WebAPI does not initialize branding. This has been corrected in AudienceView 6.7.0.
If no branding has been specified, use the default branding will be used/loaded.		 AVD-1454
When requesting WebAPI/session?DETAILS=Printers, an error occurs even though Printers is a valid node. This has been corrected in AudienceView 6.7.0.
The auditHistory parameter value has been added to toXML and toJSON node method invocations. It is now possible to request WebAPI/session?DETAILS=Printers.
Caution
The ticket stock values in the stock list cannot contain any spaces in either the 'Key' or 'Entries' fields. This will be corrected in a future release (AVD-1108).
AVD-1460
The work message is in an inconsistent location between the Java and ASP versions. In ASP, the work message is under the data object; however, in Java, the message is not under the data object. This has been corrected in AudienceView 6.7.0.
The JSON WebAPI response incorrectly assumed that a data element always followed the result. It is now conditional.		 AVD-1461
Exception details are not being returned. This has been corrected in AudienceView 6.7.0.
The exception details are now being returned.		 AVD-1462
The WebAPI has a hard-coded return data limit. If limit is reached, return message is Response was too large. Request Failed. Request a smaller collection of data. This has been corrected in AudienceView 6.7.0.
The hard-coded limit has been removed and is now determined by the IIS/Tomcat configuration to restrict the response size.		 AVD-1465
In api.asp page, the exception object is being printed rather than the object properties. For example: <message>WepAPI call ended due to uncaught exception:[object Error]</message>.
Instead of displaying exception e, should be exception e.ErrorNumber + e.Description. This occurs in multipul try/catch blocks in api.asp.		 This has been corrected in AudienceView 6.7.0. The correct error object is being displayed. AVD-1477