---
title: "How do I create multiple versions of a Luminesce provider?"
slug: "how-do-i-create-multiple-versions-of-a-luminesce-provider"
updated: 2025-02-14T12:43:57Z
published: 2025-02-14T12:43:57Z
canonical: "support.lusid.com/how-do-i-create-multiple-versions-of-a-luminesce-provider"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://support.lusid.com/llms.txt
> Use this file to discover all available pages before exploring further.

# How do I create multiple versions of a Luminesce provider?

You can specify the `ProviderNameExtension` parameter while querying [Sys.Admin.Lusid.Provider.Configure](/v1/docs/how-do-i-configure-luminesce-entity-providers-to-readwrite-properties) to create a new version of a provider.

This allows you to configure multiple versions of the provider with different [inlined properties](/v1/docs/how-do-i-configure-luminesce-entity-providers-to-readwrite-properties). Your end users can then query their own version of the base provider with only the inlined properties that are relevant to them.

## Setting up a new version of a provider

To create a new version of a provider, use the following syntax:

```sql
@keysToCatalogue = values
('<key>', '<name>', <boolean>, '<description>');

@config = select column1 as [Key], column2 as Name, column3 as IsMain, column4 as Description from @keysToCatalogue;

select * from Sys.Admin.Lusid.Provider.Configure
where Provider = '<provider-name>'
and Configuration = @config
and ProviderNameExtension = '<extension-name>';
```

[Read more about the Sys.Admin.Lusid.Provider.Configure syntax.](/v1/docs/how-do-i-configure-luminesce-entity-providers-to-readwrite-properties#using-the-sysadminlusidproviderconfigure-provider)

For example, to ‘inline’ `Instrument/Analytic/Yield` in a new version of the [Lusid.Instrument.Equity](/v1/docs/lusidinstrumenttype-reader-providers) provider:

```sql
@keysToCatalogue = values
('Instrument/Analytic/Yield', 'Yield', False, 'A property representing the instrument yield');

@config = select column1 as [Key], column2 as Name, column3 as IsMain, column4 as Description from @keysToCatalogue;

select * from Sys.Admin.Lusid.Provider.Configure
where Provider = 'Lusid.Instrument.Equity'
and Configuration = @config
and ProviderNameExtension = 'Yield';
```

Once created, the Luminesce catalogue displays your new provider version (note you need to click the **Refresh** icon to see the new version): ![](https://cdn.document360.io/d575ad81-c0ed-4980-bbd1-d59ac5c3de82/Images/Documentation/image(522).png)

## Querying a provider version

Once published, and providing suitably permissioned, an end user can [write a Luminesce SQL query](/v1/docs/understanding-the-luminesce-sql-query-syntax) using the new provider version in the same way as any other view or provider in the Luminesce catalogue.

For example, the following query retrieves the first 10 equity instruments with yields above 0.25:

```sql
select * from Lusid.Instrument.Equity.Yield where Yield > 0.25
```

## Deleting a provider version

To remove the provider version from the Luminesce catalogue (which means it will no longer be available for end users to query), use the following syntax with `WriteAction = ‘Reset’`:

```sql
@@keysToCatalogue = select '' as [Key];

select * from Sys.Admin.Lusid.Provider.Configure
where Provider = '<provider-name>'
and Configuration = @@keysToCatalogue
and ProviderNameExtension = '<extension-name>'
and WriteAction = 'Reset';
```

For example, to delete the provider version [created above](/v1/docs/how-do-i-create-multiple-versions-of-a-luminesce-provider#setting-up-a-new-version-of-a-provider):

```sql
@@keysToCatalogue = select '' as [Key];

select * from Sys.Admin.Lusid.Provider.Configure
where Provider = 'Lusid.Instrument.Equity'
and Configuration = @@keysToCatalogue
and ProviderNameExtension = 'Yield'
and WriteAction = 'Reset';
```