Back

SmartConnect: Why Extender Bulk Data Source Windows Fail to Populate in Dropdown

Published: Sep 15, 2025
Post Author Written by Amit Chaudhari

Extender Bulk Data Source Windows Failing to Populate?

While setting up the Microsoft Dynamics GP Extender Bulk Data Source, the extender window or form does not populate as expected. The goal here is to create an integration using extender data as the source and send it to the correct destination.

If you’d like to watch a video explaining this, see below or click here.

Extender Bulk Data Source

As you can see, the Extender ID is not displaying the expected name.

Extender Bulk Datasource 1 1

SmartConnect expects the view name to match the window name in order to populate the data. Technically, it is running below SQL query to get data.

SELECT DISTINCT 
     rtrim(Extender_Window_ID) AS WindowID
	,rtrim(Extender_Window_Name) AS WindowName
FROM dbo.sysobjects
INNER JOIN dbo.EXT20100 
 ON replace(rtrim(Extender_Window_ID), ' ', '') 
 IN (SELECT name FROM dbo.sysobjects WHERE type = 'V')

Because the names do not match, we need to create a view using the Views option, which generates a SQL view within the company database.

SQL Name must match the Extender Window ID.

GP Connection Extender 2

If the Views option isn’t available (as may be the case in an older version of Extender), then we need to create the view directly in SQL Server, referencing the Extender table.

Now the correct name should be populating. Please see the result below:

GP Connection Extender 3

Have a question? Please reach out to us at support@eonesolutions.com

Feeling stuck? Get the support and guidance you need to help you power through any data challenge

We're on your integration team. Connect with our people and let us know how we can help you.