forcedotcom / forcedotcom/wsc

Issues with geolocation fields and picklist value sets

Open
#321 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
Java
Stars
276
Forks
223
PR merge metrics
No merged PRs in 30d

Description

Hello,

I'm using the Maven dependencies to request Metadata API and I have two issues :

1. Geolocation Fields
There's a known issue (https://issues.salesforce.com/issue/a028c00000mNUARAA4) explaining that some data is missing in Salesforce's WSDL. But on different sites, I saw that a workaround exists by editing manually the WSDL. Is it possible to fix that issue ?
Because it causes errors and when using the Maven Dependencies, we can't do anything.

2. Picklist Value Sets
For all picklist values, no matter if they are in standard value set, custom values set, or just in fields, the Metadata API returns "isActive = false" is the value is inactive. But it doesn't return anything if the value is active. So, in the Maven library, we always get "isActive = false". If the value is active, we also get "isActive__is_set = false" but we can't use that property in our code because it's protected or private. Is it possible to return "isActive = true" if the Metadata API doesn't return a value for this field?
You can find an attachment I received from Salesforce support to explain this.
[Retrieve Picklist using API.pdf](https://github.com/forcedotcom/wsc/files/12772608/Retrieve.Picklist.using.API.pdf)

Thank you in advance for your help !

Best Regards
Cem

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with the Maven dependencies and Metadata API behavior described in the issue, using the linked Salesforce WSDL report and attached picklist PDF as context. Reproduce the geolocation-field errors and the missing active picklist values. Done means both cases are handled without manual WSDL edits and active values are represented as active in the library.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
api
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.