Following! We are evaluating the possible implementation of CSQL and these potential gotchas are important 
️
@romihache I spoke with our COM on this yesterday; confirmed there is no functionality in the UI to add additional fields to the CSQL Lead/Opportunity payload. It may be possible to have a backend team make changes, but I was asked if that was a route I wanted to take I’d need to submit a support ticket, and support would be able to check and confirm if it is possible or not.
Everything considered, my decision is to configure CSQLs sync options to Gainsight only (Lead records created in the GS Leads MDA) then use a rule to push to Salesforce. The thought process there is 1) may be quicker to build/deploy the solution than a support ticket > backend team and 2) allow us to control the setup - if we needed to change the configuration in the future then we’re not dependent on a GS backend team making changes. I’ve still to check if it’s possible to use RTR to sync to SFDC Leads object, but I’m presuming it will need to be a Horizon rule running on cadence.
I really appreciate the walkthrough and advice @Stuart !
I’m saving this conversation for future reference
It’s worth noting that taking this route will mean the lead will always be created by the integration user in SFDC; if you need to track Leads by individual users I’m guessing this would require another field to be passed (and maybe created?) in Salesforce, and some sort of workflow in SFDC to take the actual lead creator and overwrite the created by field in SFDC. We’re not tracking Leads with this granularity.
Again, thank you for taking the time to explain this in such depth! 
This needs to be turned into an idea to fix the status quo. I can’t express my disappointment at having to build a feature that exists from scratch because it’s lacking key functionality.
Hi @stuart and @alizee
Can you please share what fields were you looking forward to add in CSQL ?
Are they part of some other standard object in gainsight ?
Hi @Ritika Jindal Custom fields and fields available through lookups to the company or relationship object.
Custom fields you can add un CSQL @alizee lead object . Yes lookup to company and relationship object capability is not there. Can you please help me understand your use case where lookup to company and relationship object would help in CSQL?
@Stuart can you may be rephrase the heading of this community post as capability to add lookup fields from company and relationship object or any other object you might need ? If we get good number of requests from different customers it will help us put it in roadmap. You can even create a new request .
@Ritika Jindal Lookup fields work everywhere else or almost, so they need to work here too. It’s about parity.
Salesforce requires a number of fields to be parsed to write leads, amongst which some company details (address, phone, etc.) which exist at the company level or relationship level. This is going to be different on a company by company basis so we cannot have any form of limitations in the product on that front.
So why would I have to create static fields in GS Lead for the CSx to populate manually to be able to write the leads to SFDC since I can’t set this up in the connector job and I also CANNOT display them in the detail view. First of all, they would soon give up. Second of all, it makes no sense as they may not have the latest or it will take them more time to generate the lead.
Furthermore, the hidden filter that limits the writeback to “Gainsight” sourced leads is not appropriate. We each have our own denomination for the CSQLs and Gainsight is not the source we use. We need this to be configurable.
Hey, Community!
The Salesforce Connector article has been updated to include information about the OOB Lead Sync job and how admins can configure additional field mappings. We appreciate your valuable inputs, so please keep sharing your feedback and suggestions.
FYI @Ritika Jindal @rahul_prayakarao @shayerisen @neelam_mukherjee