April 2023 Rollup

[jmclaren]

The message below is a reposting of the developer changelog post for convenience. If there are any differences the official changelog post is to be seen as the source of truth.

---

April showers bring new HubSpot powers. Better validation for multi-currency accounts, new phone property type, improved and consolidated UIs, session timeout control for private content, and import tool improvements.

Developer Updates for April 2023

New Currency Validation for Multi-Currency Accounts Using Products API

A new currency validation will be available to multi-currency-enabled accounts using the Products API starting April 26th. This validation ensures currency values submitted via the API for the price property and the hs_price_{homecurrency} property are the same. 
Developers who submit different values for price and hs_price_{homecurrency} in the same request will receive a 400 validation error response with the following message, “Provided different values for price and hs_price_{homecurrency} properties. Please provide a valid price in the portal’s home currency: {homecurrency}”.

Snowflake Data Share: New Data Share Status Monitoring View

A new secure view has been added to Hubspot data share, allowing users to receive real-time updates on the status of the Hubspot Snowflake integration, including any potential issues affecting data sharing. To utilize this feature, users can query the data_share_status view:

select * from hubspot.public.data_share_status limit 1

The view provides updates on the integration status in reverse chronological order, allowing you to stay up-to-date with any changes or issues. Consider integrating the results of this query into a dashboard to track the integration's performance and detect any downtimes or outages.

Embedded types now available in the ‘Pop-up CTAs’ tool. The tool is renaming as CTAs and merging with existing CTAs under one nav item.

Pop-up CTAs' now offer the ability to also create embedded buttons and banners and are merging with ‘Calls-to-action’ under one nav item ‘CTAs’. Learn more on our Knowledge Base article.

New GraphQL API Availability for Service Hub and Sales Hub Enterprise Customers

Starting May 1st, HubSpot customers with Service Hub and Sales Hub Enterprise accounts can now customize the CRM with the HubSpot GraphQL API to fetch CRM data and its associations for creating custom CRM cards and tabs. This feature enables developers to make a single API call with the GraphQL endpoint: /collector/graphql. It reduces the complexity, and multiple API calls it previously took to fetch CRM object data and associations.

Now developers can utilize the GraphQL endpoint to query data or the GraphiQL explorer UI to make test calls and assist in writing queries. Currently, the GraphQL functionality supports querying for HubDB, default CRM objects, and custom CRM object data.

New “Phone Number” Property Type

The "phone number" field is a new property type used to store custom phone numbers in the CRM. We offer three default phone number properties: phone, mobile phone, and fax. These properties automatically format and validate numbers stored in the CRM. With this update users can now create custom phone number properties that take advantage of the same validation/formatting features. 

How to use this new property:

• Create a new property and select "phone number" or convert an existing custom property.
• Existing values that have a country code are valid will be formatted automatically. ex. ("+18884827768")
• To include an extension enter 'ext'. ex. ('+18884827768 ext 123')
• If you prefer to not use automatic formatting, you can click "remove number formatting" below the field. This will remove all formatting and allow you to enter any characters. To apply formatting to an unformatted number, click "apply number formatting" underneath the field.

Configurable Session timeout for private content

HubSpot is introducing session timeout for private content, which will force our customers' members to login again after a user has exceeded a preset inactivity period.

When the customers' members exceed the inactivity duration, the browser refreshes and returns the member to the login page. The member must log in again for access.
Session timeout is inactive by default. To activate, customers with website settings permission must navigate to the Private Content settings menu and select a domain to edit. Once the domain is selected, they may opt into idle session timeout by selecting the checkbox. The customer will then be prompted to select the duration that a user can remain inactive before its members are logged out. The available options are 20 minutes, 40 minutes, 60 minutes, and 1 day. Once selected, the customer will need to save the new settings.

For more information, please check out the Knowledgebase article.

New Export Feature for Private Apps API Call Log Data

We’re excited to announce that starting April 26th, HubSpot released this feature to the public, and all HubSpot customers can access their private app call logs.

This feature provides API call log data within HubSpot for the last 30 days. To export the private app logs, navigate to the private app itself, and within the app’s page, click on the “Logs” tab, then the “API calls” tab. Next, you will click “Export logs,” and then you can filter the data logs based on a specific date frame. The logs are exported in a CSV file format and found in the user’s notification center.

Public Betas

The following are functionality betas that you can take part in.

An updated user interface for CMS content editors

The HubSpot CMS has undergone a lot of changes over the past few years, adding new features and functionality, and changing the way users create content. The user interface of the editor needs to also grow and change to accommodate all of these latest innovations and user behaviors.

This new UI was designed to give the user more space to view and interact with their content, while also keeping more editing features close at hand. The familiar File/Edit/View/Help navigation to keep content admin tasks easy to find and use, while it uses an expanding sidebar on the left hand side of the screen for easy access to content editing tasks.

Watch a demo of the new interface on our HubSpot Developer YouTube channel.

This beta is not available in the "Product Updates" screen but you can sign up to try it.

Navigation Element Import

When migrating a website and importing site pages into HubSpot, you can now also import website navigation. This feature is in beta and available to all versions of CMS Hub.

How does it work?

1. Go to your Website Settings
2. If you don't have an existing blog. Select "Import Blog". If you have an existing blog the "Import Blog" option will appear in the field for changing which blog you're editing.
3. Select "Start new import"
4. Select "Website pages"
5. Enter in the respective Website URL
6. Review results
7. Select your pages & menu elements you'd like to import
8. Import

If you are interested in learning more and gaining access to this beta or other betas, you may visit the Product Updates > Early Access > Betas section within your account settings. 

Questions, comments? lets's chat below.

[jmclaren]

I apologize for a slow response here, the team has worked on a lot of improvements to the new interface addressing many of the issues noted here. If you have further feedback let us know I'll make sure the team sees it.

[CFrishe]

The new CMS content editor beta takes the existing very user-friendly interface with easy access to everything and makes it unnecessarily complicated. Where you currently have everything at your fingertips, the new beta forces you to dig around for what you use most often. The biggest issue is related to creating new pages. With the existing editor, all modules are easily available for use in setting up or adding to pages, and if you need more room you can easily minimize the sidebar. In the new Beta, the modules are hidden in a fly-out menu that takes up so much of the screen as to make it practically unusable unless you are using a 4K resolution monitor. The new interface will have a severely negative impact on productivity. 

[AdeleTib]

Not loving the new CMS content editor (beta). Takes up way too much screen space and doesn't feel like it adds much value to the editing experience. Were the changes driven by user requests or user tracking/observations by the team?

[AOConnell23]

Is anyone experiencing issues where their embedded forms are defaulting to a white background instead of transparent? Does anyone have thoughts to override this?