What problem are you observing?
Accounts scanned goes to 0 (previously 2800+) with bad mapping.
My field ‘utcOffset’ was setup as an int. My actual data coming in was a string from the Web Services (VA) connector. ex. “GMT-08:00 Pacific Time (Los Angeles)”
This causes zero accounts to be found during a scan. Effectively deleting all accounts if the threshold weren’t set because this is my primary Identity Profile source.
What is the correct behavior?
The field should be ignored if it doesn’t match or marshal to the correct schema type. It shouldn’t cause an account to be completely ignored.
Bugs are considered issues with a feature that prevent it from behaving as designed. In what way do you believe this feature is not working as designed?
This should map a null instead of removing the account from the source.
What product feature is this related to?
Identity Now. Web Services Connector (Source Type:Web ServicesConnection Type:Direct Connection)
Please indicate which product and feature you are having issues with. Please include version numbers and any other relevant information.
Current sandbox version of IDN.
What are the steps to reproduce the issue?
Add a schema attribute as an ‘int’. Setup your web services response to map a string value into that int. Here are the unique values that would have been mapped in from the source, in case the values themselves are problematic and not strings in general:
GMT-05:00 Eastern Time (New York)
GMT-06:00 Central Time (Chicago)
GMT-07:00 Mountain Time (Denver)
GMT-08:00 Pacific Time (Los Angeles)
GMT-09:00 Alaska Time (Anchorage)
GMT-10:00 Hawaii-Aleutian Standard Time (Honolulu)
Please share a complete and detailed list of steps that others can follow to reproduce this issue. Include links, images, and other supporting information to help us reproduce this. Issues that can be reproduced are more likely to be prioritized.
Do you have any other information about your environment that may help?
sandbox.