You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hop.apache.org by "gertwieland (via GitHub)" <gi...@apache.org> on 2026/01/03 20:40:20 UTC
[I] [Bug]: Salesforce Input sets metadata for all fields to 'String' (hop)
gertwieland opened a new issue, #6292:
URL: https://github.com/apache/hop/issues/6292
### Apache Hop version?
2.16
### Java version?
openjdk version "17.0.13" 2024-10-15
### Operating system
Windows
### What happened?
Hop 2.16 reads all Saleforce input fields as String. As a result, boolean fields are not showing the expected values Y/N, but true/false. Even worse, when hitting "Get fields", it shows the correct data types. However, after saving, it just sets them all back to String.
It's very easy to reproduce.
Hit "Get Fields", and it shows the correct metadata.
<img width="2311" height="2241" alt="Image" src="https://github.com/user-attachments/assets/15f5584f-bbd9-4b56-934e-89581b330962" />
Do NOT save, just look at the data preview. It shows boolean fields as Y/N
<img width="144" height="192" alt="Image" src="https://github.com/user-attachments/assets/46a2e2f0-2000-486f-937a-752b50555a3e" />
Then, save the pipeline, and look at the Metadata again.
All fields are now set to String!
<img width="2152" height="2151" alt="Image" src="https://github.com/user-attachments/assets/0099baac-97fe-4174-a2c1-c6443701606d" />
Booleans now show as text "true" or "false"
<img width="183" height="372" alt="Image" src="https://github.com/user-attachments/assets/b97dd23b-93d3-4ca2-9c46-0297d75fca93" />
On our end, this created quite a disaster because a good part of our access control automation is based on such checkboxes. Access is typically granted where values are set to "Y', otherwise denied, but the logic did not expect "true", so most of the access for most of our users was suddenly denied. I'll just downgrade to 2.15 for now. I guess I'll have to be much more careful with future updates. I'll try to think of better protection mechanisms, eg. force pipelines to fail when certain fields return unexpected values.
### Issue Priority
Priority: 1
### Issue Component
Component: Hop Run
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@hop.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Bug]: Salesforce Input sets metadata for all fields to 'String' (hop)
Posted by "bamaer (via GitHub)" <gi...@apache.org>.
bamaer closed issue #6292: [Bug]: Salesforce Input sets metadata for all fields to 'String'
URL: https://github.com/apache/hop/issues/6292
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@hop.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Bug]: Salesforce Input sets metadata for all fields to 'String' (hop)
Posted by "gertwieland (via GitHub)" <gi...@apache.org>.
gertwieland commented on issue #6292:
URL: https://github.com/apache/hop/issues/6292#issuecomment-3707348161
Sorry, I just noticed that there's a report already
https://github.com/apache/hop/pull/6101
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@hop.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Bug]: Salesforce Input sets metadata for all fields to 'String' (hop)
Posted by "bamaer (via GitHub)" <gi...@apache.org>.
bamaer commented on issue #6292:
URL: https://github.com/apache/hop/issues/6292#issuecomment-3710713094
This is related to #6054 and fixed in the PR you referred to (#6101).
I just checked locally and this looks ok, but if you want to be 100% sure, you can download a development build and check for yourself. I'll close the issue for now, we can always reopen later if needed.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@hop.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org