SanfordWhiteman

SFDC Sharing Rules determine which records Marketo’s SFDC User* can see. So you’d exclude anyone with Confidential=true from Sharing Rules. *technically, Marketo’s SFDC User’s Profile

One of your competitor company was providing it through a direct REST API and we were using it (through a programmatic approach). As because your systems couldn't provide, it doesn't mean that the entire world couldn't. There’s no app that doesn’t run a query to get the real-time count of a Smart Li...

Also, I'm not sure why these threads are marked as "Answered" or "Correct Answer"Because a correct answer was provided! You can get the count using the REST API (that’s what programmatic approach means). There’s another method mentioned which is also correct. There’s no “more correct” answer than th...

If you set SFDC sharing rules to include a Boolean like Hide from Marketo then yes, you can change that field from the Marketo side and immediately break the sync (and all future syncs) for that SFDC record. However, I wouldn’t recommend you do it that way because it’s less than graceful (itinterrup...

The filter field is expected to be a Boolean. You can manage that field with SFDC Flow/Apex to have it be the result of multiple contributing fields.

the native sync creates a new Salesforce Lead instead of linking to the existing record. This is causing a lot of duplicates in SFDC.This is expected behavior. Marketo has no choice if there’s no existing record in Marketo and you choose to sync the person to SFDC. I also assume you’re stopping Mark...

That's typical.

“Best” is too subjective, there are lots of test data generators out there. I like Mockaroo myself.

I used the “in future X days” filter thinking that it would only consider date and month and not the year as the lease start date field is going to remain the same, and it successfully picked the records with the current year (2025) and the one set to 1990. No, it didn’t pick a date in 1990 as if it...

Well, please don’t post ChatGPT hallucinations here. You must test to see if they’re even close to the truth. Can’t have a community polluted by false info. In this case, even without testing, can’t see how this passes the smell test. Is the year of someone’s Date of Birth field no longer filterable...