Luminate Web Services (LWS) Release

Here are the latest changes in Luminate Web Services.

 

Version 1.46 Release Notes

May 2024

The Luminate Web Services version 1.46 release includes the following resolved issue.

 

Resolved Issue

Bug  

2593409

Valid API and Luminate Web Services calls intermittently produce an Invalid API Key error impacting integration and logins

An update was made to prevent intermittent Invalid API Key errors that occurred during API and Luminate Web Services integration and logins.

Version 1.45 Release Notes

March 2024

The Luminate Web Services version 1.45 release (previously 1.44) includes resolved issues.

 

Resolved Issues

Bug  

2768996

Support encrypted Date of Birth field in Luminate Web Services when retrieving results

When selecting Date of Birth in Luminate Web Services, the expected value of the date is returned.

2795109

ORA-00942 errors occur

ORA-00942 exceptions no longer occur when working with Luminate Web Services.

2797882

Additional logging added to Luminate Web Services

To assist Blackbaud in identifying and resolving errors such as the Invalid API Key error, additional logging was added to Luminate Web Services.

2784311

Luminate Web Services is unable to query on values with special characters

A query that contains special characters, such as an apostrophe, returns data in Luminate Web Services.

2838675

After the Luminate Web Services 1.44 release, Donation type queries or extractions encounter the following error: ORA-00918: column ambiguously defined due to multiple items having v_1

An issue in Luminate Web Services 1.44 that prevented Donation type from being queried or extracted due to a naming issue was resolved.

Version 1.43 Release Notes

November 2023

The Luminate Web Services version 1.43 release includes resolved issues.

Resolved Issues

Bug  

2598486

Add Calendar Ticket questions and responses to Luminate Web Services

You can now pull Calendar Event Ticket Question responses into your connected system to collect the Calendar Event Ticket Question answers for this feature introduced in the Luminate Online 23.1.1 release.

TICKET_CLASS_QUESTION and TICKET_CLASS_RESPONSE are now available.

To gather this data, specifically mention these fields in your query. For example, use a query such as:

select CalenderTicketQuestion from CalendarEventTicketType and select CalenderTicketResponse from CalendarEventRSVP

Specify the fields for retrieving nested results. To return calendar event results alongside parent records, ensure the is_wildcard field is set to 'T' explicitly, such as in this example:

update query_table_components set IS_WILDCARD = 'T' WHERE component_name in ('CalendarTicketQuestion', 'CalendarTicketResponse');

2460120

Luminate Web Services donation API will return duplicate rows after the first page of data

The Luminate Web Services donation API no longer returns duplicate rows of data after the first page of data.

2695679

The Payment record type is returning an undocumented value of ‘3’ for the CreationMethod of the Facebook donations causing impact to some integrations

To recognize Facebook Fundraising donations that are tracked as external transactions, the Payment record type now returns a value of EXTERNAL (3) from the CreationMethod to identify donations made to a Facebook Fundraiser.

Version 1.42 Release Notes

August 2023

The Luminate Web Services version 1.42 release includes resolved issues.

Resolved Issues

Bug Description

2574648

When querying enum types, Luminate Web Services doesn't return the options under certain conditions

Querying enum types via Luminate Web Services now renders the enum field options as expected.

2583519

After the Luminate Web Services 1.41 release, ORA-00942 exceptions occur

ORA-00942 exceptions no longer occur when working with Luminate Web Services.

2594025

Survey results return duplicate responses in the Omatic plugin

Survey results only show responses once and no longer cause duplication in the Omatic plugin.

 

Version 1.41 Release Notes

June 2023

The Luminate Web Services version 1.41 release includes infrastructure updates to support the new Facebook integration and Luminate Online privacy features, security enhancements, and resolved issues.

Product Updates

Facebook Integration

To support the new Facebook integration, a new transaction type was added to Luminate Online to track and filter donations processed by Meta Pay. The transaction type is "ONLINE_EXTERNAL".

Privacy Features

To support new Privacy features, the following improvements released:

  • The new REMOVED_DEIDENTIFIED active detail value in Luminate Online can return correctly by Luminate Web Services and is defined in the Enum/Wsdl.

  • The Contains Personal Information field was added to the Survey Question object in Luminate Web Services, so you can see which questions are marked as containing personal information when you query surveys via Luminate Web Services.

  • You can query the new DEIDENTIFICATION_LOG in Luminate Web Services to retrieve the ConsID, Request Date, Date and Status, so you can tell when a constituent was deidentified. However, the constituent won't show up in incremental queries if the constituent is removed.

  • Privacy Opt Out fields were added to Luminate Web Services so you can pull data for the four new Privacy Opt-Outs for constituents: Sale of Data, Profiling, Targeted Ads, and Global Privacy Control.

Resolved Issues

Bug Description
1764054

When querying Luminate Online for CalendarEventTicketType by ModifyDate, Ticket Types are not syncing through to Luminate Web Services as expected by the modify date
Records are properly returned according to their modify date when querying Luminate Online for CalendarEventTicketType by ModifyDate.

2292239

Luminate Web Services does not validate dateTime fields before making a REST call to Luminate Online

Luminate Web Services now validates a value in the dateTime fields before a request is sent to Luminate Online.

2438060

Luminate Web Services needs the Venmo payment type to successfully integrate Venmo gifts from Luminate Online

Venmo is now present in Luminate Web Services as a CreditCardType so data values sync properly in Luminate Online.

2455035

The WSDL is missing an enumeration for SourceCodeType for value 8, AUTORESPONDER, causing this error in the sync: "Error in deserializing body of reply message for operation 'Query'."

The WSDL now includes an enumeration for SourceCodeType for value 8, AUTORESPONDER, so that deserialization errors no longer occur in the Luminate Online sync.