topic Re: Netsuite Connector Issue in HubSpot Native Apps

Netsuite Connector Issue

SHQNY — Mon, 16 Sep 2024 16:39:58 GMT

Hi! I've encountered a strange issue in the my Hubspot > Netsuite sync, and I'm hoping someone can help me figure out a solution.

We have the sync set up so that once a Deal is marked as Closed-Won in Hubspot, it is pushed into Netsuite as an Opportunity - Won record. However, when the data is pulled into Netsuite, all of the dates entered in the Hubspot Deal show up as the day prior in Netsuite. For example, if a deal has an event date listed as 11/01/2024 on the deal record, the Opportunity record created in Netsuite will display the event date as 10/31/2024.

I have checked, and both accounts are set to the same time zone, so I don't think that is the problem. Any ideas or suggestions on how to fix this issue, or additional settings I should invesigate?

Re: Netsuite Connector Issue

Jnix284 — Mon, 16 Sep 2024 17:04:57 GMT

This is quite strange @SHQNY, happy to help see if someone I know has any ideas.

@crispyGTM @tmcginnis have either of you run into any issues where Netsuite is showing dates as the day prior to the date in HubSpot (e.g. HubSpot close date is 11/1/2024, Netsuite shows 10/31/2024) or know someone else at A8 who's worked closely with Netsuite that might have insight?

Re: Netsuite Connector Issue

tmcginnis — Mon, 16 Sep 2024 17:08:06 GMT

@Jnix284 - is the Netsuite Date field a DateTime or just a date picker? HubSpot's Close Date is datetime. When those are mapped to date pickers (without the time) it'll default to midnight UTC, the day before.

Re: Netsuite Connector Issue

SHQNY — Mon, 16 Sep 2024 17:14:43 GMT

The feilds that aren't lining up are custom feilds in both Netsuite and Hubspot, and both are date pickers.

Re: Netsuite Connector Issue

Jnix284 — Mon, 16 Sep 2024 17:36:40 GMT

Thank you @tmcginnis you're awesome, I forgot that DateTime mapped to Date Picker does this!

@SHQNY I saw your reply that both properties are custom fields that are Date Picker only, are you not using the default HubSpot Closed Won Date property?

Based on the DateTime to Date Picker conversion issue and it being so similar to what you're encountering, I feel like there has to be a connection somehow. Can you dig deeper into the custom property in HubSpot to make sure it's not a DateTime property?

Re: Netsuite Connector Issue

SHQNY — Mon, 16 Sep 2024 18:42:19 GMT

We do use the default HubSpot Closed Won Date property, and it is actually syncing correctly to Netsuite.

However, since we are selling an Event space, we needed to include the date the event will take place on the Deal record, so we created a custom Date Picker field. In Netsuite, we created a similar feild (also a Date Picker) on Opportunity records. So while the Closed Won Date is coming through to the Opportunity in Netsuite correctly, the Event Date is showing up as the date prior.

I hope this clarifies the issue!

Do you think switching them all to Date Time feilds would fix the issue?

Re: Netsuite Connector Issue

Jnix284 — Mon, 16 Sep 2024 19:29:53 GMT

@SHQNY I think it would definitely be worth testing the DateTime property to see if you can get it to sync the correct date information.

Re: Netsuite Connector Issue

SHQNY — Thu, 26 Sep 2024 17:26:13 GMT

Switching all of the fields to DateTime properties seemed to do the trick! Thank you for the suggestion!

Re: Netsuite Connector Issue

tmcginnis — Thu, 26 Sep 2024 17:34:27 GMT

@SHQNY - great news! Glad it worked out. Happy to help! 🙂

Re: Netsuite Connector Issue

erpnetsuite — Mon, 21 Oct 2024 18:28:35 GMT

Hi,

Thanks for sharing the details! It looks like the date discrepancy is related to how HubSpot and NetSuite handle date/time fields during sync, which can sometimes lead to timezone or formatting misalignments. Since you mentioned that both custom fields (Event Date) are using Date Picker fields in HubSpot and NetSuite, let’s explore a few possible causes and solutions:

1. Root Cause: Midnight UTC Default Behavior

HubSpot's Date Picker fields are stored without time components but, under the hood, the system defaults to midnight UTC (00:00).
During the sync, if NetSuite interprets this value with a different timezone (even if both systems are in the same zone), it may show as the day prior because of the time shift from midnight UTC.

2. Potential Solutions

Option 1: Switch to DateTime Fields

Updating the custom Event Date fields in both HubSpot and NetSuite to DateTime fields might resolve the issue.
Even if you don’t need time information, the DateTime fields can store and sync data more accurately across platforms, eliminating timezone shifts.
Test this solution in your sandbox environment by:
1. Changing the custom fields to DateTime in both systems.
2. Syncing a few test records and confirming if the dates align properly.

Option 2: Adjust via Workflow or Script in NetSuite

If switching to DateTime fields isn’t ideal, a workflow or SuiteScript in NetSuite could adjust the event date to correct the discrepancy during sync.
For example, you could write a script to add a day to the Event Date if it’s coming from HubSpot, ensuring consistency without changing field types.

Option 3: Middleware Adjustment

If you are open to using a middleware like Celigo, you could apply a simple transformation rule to adjust the date value before it’s pushed into NetSuite.

3. Check for Other Sync Settings

Verify if field-level mapping settings are consistent in both systems, ensuring that the field types match exactly.
Also, confirm there are no time-based workflow rules in either system that might alter the date during the sync.

I’d recommend starting with Option 1 since using DateTime fields is often the cleanest fix for these types of issues. Let me know how it goes or if you need further help implementing a solution!

Best regards,
David
NetSuite & HubSpot Integration Specialist