New board topics in Microsoft Fabric Community

Best practice for loading Salesforce data into Fabric with deleted records

RMori95610 — Wed, 16 Sep 2026 01:53:21 GMT

Hi Fabric Community,

We are currently evaluating the best way to load Salesforce data into a Microsoft Fabric Lakehouse.

We would like to keep the implementation and ongoing operation as low-code as possible, and we are currently considering the following three options:

Dataflow Gen2 + Pipeline
- Use the Salesforce Objects connector in Dataflow Gen2 to retrieve Salesforce data.
- Load the data into a Lakehouse.
- Use a Pipeline to run the Dataflow Gen2 on a schedule.
Pipeline + Copy Activity
- Use the Salesforce Objects connector directly in a Copy Activity within a Pipeline.
- Copy Salesforce data directly into the Lakehouse.
Copy Job
- Use Salesforce as the source and the Lakehouse as the destination.
- If necessary, invoke the Copy Job from a Pipeline using a Copy Job Activity.

In addition to active Salesforce records, we also need to retrieve records that have been deleted in Salesforce and retain them in the Lakehouse with a deletion flag such as IsDeleted = true, rather than physically removing them from Fabric.

For example, we would like to preserve the Salesforce record state in the Bronze layer as follows:

Id	Name	IsDeleted
001	Company A	false
002	Company B	true

We would then update the latest state in the Silver layer using the Salesforce record ID as the key. For downstream use cases such as AI, we would normally use only records where IsDeleted = false.

For this initial implementation, we are not planning to use a watermark-based incremental load. Our current goal is simply to determine the most appropriate ingestion method from Salesforce into Fabric.

My current understanding is that the Salesforce source in Copy Activity provides an "Include deleted objects" option, so option 2 appears to support retrieving deleted Salesforce records.

However, I am not sure how the same requirement should be handled with Dataflow Gen2 or Copy Job.

I would appreciate your advice on the following questions:

If we want a low-code implementation and also need to retain deleted Salesforce records in the Lakehouse with an IsDeleted flag, which of the three approaches would you recommend?
Can Dataflow Gen2 retrieve deleted Salesforce records in a way equivalent to the "Include deleted objects" option available in Copy Activity? My understanding is that simply selecting the IsDeleted field may not be enough if deleted records are excluded from the Salesforce query itself.
With Copy Job, is it possible to retrieve deleted Salesforce records and retain them in the Lakehouse with IsDeleted = true? In this case, I am not asking about detecting deletes through watermark-based incremental loading or CDC. I would like deleted records to be included as part of the Salesforce data retrieval itself.
If there is another recommended low-code architecture for loading Salesforce data into a Fabric Lakehouse while retaining deleted records, I would also be interested in hearing about it.

If anyone has implemented a similar Salesforce-to-Fabric ingestion pattern in production, or knows the recommended approach in Microsoft Fabric, I would greatly appreciate your experience and advice.

Thank you in advance.

Can a service principal with federated credentials be used for SQL cloud connection auth?

CharlieFab — Wed, 16 Sep 2026 00:00:14 GMT

Replacing OAuth 2.0 personal-account auth on our Fabric SQL cloud connections. Workspace identity doesn't fit, because semantic models in other workspaces share the same connection and each workspace has its own identity — those refreshes fail with invalid credentials unless every workspace identity is granted on the database.

A service principal solves that, but I'd like to avoid storing a secret. I added a federated identity credential to the app registration. In the connection settings, Service Principal auth only offers a key or a certificate, with nowhere to reference the federated credential.

Is that expected? I assume federation needs the caller to present a token it already holds, and the Fabric refresh engine has none — so it simply can't apply. Confirmation would be useful, as would any roadmap or Ideas link for secret less cloud connection auth.

If certificate is the answer, I'd also welcome hearing how others handle cert rotation across many connections given the encrypted payload on the update credentials API.\

Power BI semantic model refresh fails in Service, but Gen1 dataflow and Desktop refresh successfully

Teddddddddddddd — Tue, 15 Sep 2026 23:53:57 GMT

Hi everyone, my semantic model refresh fails in Power BI Service with this error:

DataFormat.Error: The input couldn't be recognized as a valid Excel document.
Microsoft.Data.Mashup.ErrorCode = 10311.
The exception was raised by the IDbCommand interface.

However:

The Gen1 dataflow refreshes successfully.
The model also refreshes successfully in Power BI Desktop.
I’ve reviewed the Power Query queries and couldn’t find any problems.

The failure appears to happen only when refreshing the semantic model in Power BI Service. What could cause this difference, and how can I identify the specific query or source triggering the error?

Error details:

Cluster: WABI-SOUTH-EAST-ASIA-redirect.analysis.windows.net
Activity ID: 76273612-20ed-4ca2-988e-4f593db29fa5
Request ID: 42e32479-4c91-40cf-b83c-e1ebd9591dc4
Time: 2026-09-15 20:18:51 UTC

Any help would be appreciated.

Office 365 Outlook activity cannot bind Workspace Identity or Service Principal connection

vicenteajm — Tue, 15 Sep 2026 23:47:21 GMT

Hi Fabric Community,

I am testing the Office 365 Outlook / Office 365 Email activity in Microsoft Fabric Data Factory for a CI/CD scenario.

According to the current Microsoft Learn documentation, the Office 365 Outlook activity supports User Authentication OAuth, Workspace Identity WI, and Service Principal SPN.

I tested both Service Principal and Workspace Identity.

The Fabric workspace has an active Workspace Identity.

The corresponding Microsoft Entra application and service principal exist.

The Office 365 Email / MicrosoftOutlook cloud connection can be created successfully.

The connection is visible in Manage connections and gateways.

From the pipeline Outlook activity, the connection is also visible through Browse all.

The issue is that when I select the WI or SPN connection from Browse all, Fabric shows the loading indicator but does not bind the connection to the Outlook activity.

No error is displayed.

The problem occurs before pipeline execution, so this is not a Microsoft Graph Mail.Send runtime error.

Expected behavior:

The selected Workspace Identity or Service Principal connection should be associated with the Office 365 Outlook activity.

Actual behavior:

The connection is visible and discoverable, but selecting it does nothing and the activity remains without a connection.

This blocks our CI/CD scenario because we want to avoid user OAuth connections that must be recreated or rebound between DEV, TEST and PROD.

I also noticed a documentation inconsistency.

The current Office 365 Outlook activity documentation explicitly says that Workspace Identity and Service Principal are supported.

However, the general Service Principal support page does not currently list Outlook as a supported data source.

The general Workspace Identity support page also does not list Outlook among the supported data sources.

Can Microsoft confirm whether Workspace Identity and Service Principal support for the Office 365 Outlook activity is fully GA, under staged rollout, or currently affected by a known issue?

Microsoft Learn references:

Office 365 Outlook activity

learn.microsoft.com/en-us/fabric/data-factory/outlook-activity

Service Principal support in Data Factory

learn.microsoft.com/en-us/fabric/data-factory/service-principals

Workspace Identity support in Data Factory

learn.microsoft.com/en-us/fabric/data-factory/workspace-identity

I can provide additional diagnostics or tenant details privately if required.

Thanks.

Free Exam Vouchers - DP-600, DP-700 or DP-800

philippaburgess — Tue, 15 Sep 2026 23:31:20 GMT

Following up on Haider's Discussion Post:

Free Exam Voucher Interest Form

https://forms.gle/ErqTGaRw3m43yoYq7

Hide a Page within APP

Pooja_Kumar — Tue, 15 Sep 2026 21:24:44 GMT

Hi,

I have two level of users where
1. set of Users should access page1,2,3
2. set of Users should access page 1, 2

Any suggestions on how to achieve this without replicating the report in the Power bi App

Configure Dataflow Gen2

UncleLewis — Tue, 15 Sep 2026 20:31:27 GMT

Hi,

Using DataFlow Gen2
I don't see a gear icon anywhere near default destination so I can configure

What am I missing?
Thanks,
w

RDL Subscription Errors When Saving to SharePoint

MarkPalmberg — Tue, 15 Sep 2026 20:23:06 GMT

Hi.

I have a paginated report in an app. The app is permissioned to a couple groups of users. Those users can run the report and export the output via the app.

Those users permissioned to the app can also set up a subscription that sends the report output to them via email.

What the users can't do is specify a SharePoint folder in their subscription for the output of the report, even though the same permissions groups on the app have access to the SharePoint site. Here's the error the users get when trying to save the subscription:

I'm able to specify the SharePoint folder in question and execute a subscription that exports the report output successfully. The only difference between me and the users who only have app-level access to the report is that I'm in a group that has member access to the workspace where the app and report reside. I'm baffled that that difference would prevent users from being able to export to a SharePoint site, but...here we are.

How to display images from Dataverse on Power Bi Report Builder

Fern_21 — Tue, 15 Sep 2026 19:10:57 GMT

Hi all!

On Power BI Report Builder I need to display images I have on Dataverse. What format should they be in? Base64? Also, I should be able to change the images based on the filters I select. Is it possible? Thank you so much

This semantic model uses a deprecated gateway version. Upgrade required.

DClark21044 — Tue, 15 Sep 2026 16:35:08 GMT

I started getting the following message on nearly every report on my tenant suddenly. The gateway has been updated the same way with the same cadence for years without have this message appear.

The gateway is one update behind the newest. Was able to get the message to go away for most users by restarting the gateway but the message still persists for some. Everything is working fine but as you can imagine, it's causing lots of panic. Any input would be greatly appreciated.

How can I automatically clear a slicer selection?

Afsaneh25 — Tue, 15 Sep 2026 14:57:01 GMT

Hello,

I have a Power BI report page with three dropdown slicers, all configured as single-select. Based on the selections in these slicers, a fourth slicer, displayed as a vertical list, is dynamically filtered to show a list of options from a column in one of my tables.

When I select an option from the vertical slicer, the related information is displayed in several charts and tables.

However, I am experiencing an issue when changing the selections in the three dropdown slicers.

For example:

Suppose I select X in one of the dropdown slicers. The vertical slicer then displays X1, X2, X3, ....
I select X1 from the vertical slicer, and the charts and tables update accordingly.
Without manually clearing X1, I change the dropdown selection from X to Y.
The vertical slicer now displays Y1, Y2, Y3, ..., but X1 remains selected in the slicer.
Because X1 is not part of the available options under Y, the charts and tables become empty.

My question: Is there a way to automatically clear or reset the selection in the vertical slicer whenever one

of the three dropdown slicers changes?

Ideally, when I change the dropdown selection from X to Y, the vertical slicer should automatically clear its previous selection so that I can select an option from the new list (Y1, Y2, Y3, ...).

I would appreciate any suggestions or recommended approaches. Thank you!

Need to Migrate SP written in Synapse to Fabric

maxravi — Tue, 15 Sep 2026 14:50:23 GMT

Hello,

I need to migrate my stored prodecure SP from synapse to Fabric, can you please help me with best approach. I am seeing a lot of syntax changes. Suggest me some best, quickest and efficient ways to migrate.

Thanks,

How can I create cards with trend percentage and mini sparkline chart like this dashboard?

Rutvika — Tue, 15 Sep 2026 14:39:29 GMT

How can I recreate cards with a metric value, MoM growth indicator, and a sparkline trend line inside the same card in Power BI? Is this achievable using native visuals or does it require a custom visual? Screenshot attached for reference
Requirement:
1.the card on hover should have glow and shadow ( as shown in screenshot for M365 Groups)
2.on default the glow and shadow should disappear (as shown in screenshot for Total Mailbox)

Not able to extract direct lake semantic models through api

Anmoldeep — Tue, 15 Sep 2026 14:25:56 GMT

I’m trying to retrieve the item definition of a Power BI semantic model using the Fabric REST API, but the request is failing for some semantic models.The API returns the following error:

RuntimeError: Get Item Definition failed.Dataset Workload failed to export the dataset with dataset id . We cannot load this Direct Lake dataset because your Power BI capacity does not support Direct Lake mode. Please use a Power BI capacity type that supports Direct Lake mode.

The semantic model is using Direct Lake mode.

Is Get Item Definition / Fabric REST API supported for Direct Lake semantic models only when the workspace is on a Fabric-supported capacity?
What specific Power BI/Fabric capacity SKUs support Direct Lake?
Is there any way to retrieve the semantic model definition/TMDL for a Direct Lake model when the workspace is on a capacity that doesn't support Direct Lake?
Could this error also occur if the model was originally created as Direct Lake but the current workspace/capacity configuration has changed?
Are there any recommended APIs or alternative approaches for extracting metadata (tables, columns, measures, relationships, etc.) from Direct Lake semantic models in this situation?

I would especially appreciate clarification on whether this is an API limitation, capacity limitation, or a limitation of the Direct Lake workload itself.

Thanks!

Databricks Mirroring - Direct Lake and Dynamic RLS/ Masking Access Controls

henry_gonsalves — Tue, 15 Sep 2026 13:59:52 GMT

I want to set access controls for our data in a single place within databricks unity catalogue and have a user's credentials passed back to databricks platform and the relevant data returned on the Power BI report. This seems to works well for direct query but I'd like to ensure that reports are performant for users which may not always be the case using direct query with larger datasets/ models

I've been looking into Direct Lake and have the following questions:

Will we need to set-up databricks/ unity catalogue mirroring with Fabric to enable Direct Lake?
Will there be a performance increase using Direct Lake for databricks over Direct Query connections?
Will I be able to pass back user's credentials back to source to enforce the masking and RLS set within table access policies in dataricks using a Direct Lake connection?

It seems like there are performance benefits to Direct Lake but I am unsure whether RLS and column masking is enforced like Direct Query connections. I don't want to recreate access controls within the Power BI semantic model, ideally.

Can anyone provide the best architecture for working with databricks that is both performant, secure and easy to manage? Is anyone able to provide a practical example of OneLake security and how this applies to mutiple sources and the effect in Power BI? Thanks

Paginated reports and direct query live refresh after PBI GWs update to 09/2026 from 12/2025

STANHTPS — Tue, 15 Sep 2026 13:12:26 GMT

hello everyone,

This is not a spam. I am Windows server Administrator in Czech Republic. I need your help with this case.

Has someone experinced the same issues? Paginated reports should return the easy results with three records from Oracle table but instead it is still loading and cannot render the report, it should take only few seconds. Refresh of report with direct query live return the screen: (sry it is in the czech language :-( ) First of all, I found out that since May 206, the PBI version includes the built in Oracle ODP provider, so I did disable it in Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.dll.config, and also tried to change MashupDefaultPoolContainerMaxWorkingSetInMB from 0 to 8192MB(VM Hyper-v server has more), but the paginated reports are still not working at all and direct query too. I have few more hours to try to solve it, then have to recover the virtual machine to the previous deprecated September 2025 version and try to update to March or April 2026, without any changes that probably causes the errors.

Thank you very much community for help.

Paginated reports and direct query live refresh after PBI GWs update to 09/2026 from 12/2025

STANHTPS — Tue, 15 Sep 2026 12:55:27 GMT

hello everyone,

Has someone experinced the same issues? Paginated reports should return the easy results with three records from Oracle table but instead it is still loading and cannot render the report, it shold take only few seconds. Refresh of report with direct query live return the screen: (sry it is in the czech language :-( ) First of all, I found out that since May 206, the PBI version includes the built in Oracle ODP provider, so I did disable it in Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.dll.config, and also tried to change MashupDefaultPoolContainerMaxWorkingSetInMB from 0 to 8192MB(VM Hyper-v server has more), but the paginated reports are still not working at all and direct query too. I have fwew more hours to try to solve it, then have to recover the virtual machine to the prevousl deprecated september 2025 version and try to update to march or april 2026, without any changes that probably causes the errors.

Thank you very much community for help.

Power bi Refresh Failure

Rohit_Agrawal — Tue, 15 Sep 2026 11:51:36 GMT

**Title: Scheduled refresh timing out (5hr XMLA limit) — ServiceNow REST API via Web.Contents, no query folding, incremental refresh not viable**

Hi all,

I'm hitting a wall with a dataset that pulls from ServiceNow via the Table API and would appreciate any guidance from people who've dealt with non-foldable REST sources at scale.

**Setup**

- Source: ServiceNow Table API (`/api/now/table/incident`, `change_request`, `problem`, `sc_req_item`, `task`, and a custom `u_change_deployment` table) — 6 tables total in one semantic model

- Connector: `Web.Contents` with `sysparm_query`, `sysparm_fields`, `sysparm_limit`, `sysparm_offset` passed through the `Query` record (static base URL, so no dynamic data source issue)

- Paging: `List.Generate` loop, page size 5000, looping until an empty page returns

- Volume: roughly 365,000 incident records for the current year, plus large RITM/task volumes having approx 10 lakh rows and 30 columns

- Capacity: Power BI Pro / shared capacity, North Europe

- Refresh: scheduled daily

**Problems I'm facing**

**1. No query folding.** `Web.Contents` isn't foldable, so every transformation (expand record column, type changes, filters) runs locally in the mashup engine after the full payload is pulled. "View Native Query" is greyed out on every step, as expected. I've done what I can by pushing the date filter into `sysparm_query` so ServiceNow returns only the relevant range, but that's manual server-side filtering, not folding.

**2. Incremental refresh flags the query as non-foldable.** The IR dialog shows "Unable to confirm if the M query can be folded. It is not recommended to use incremental refresh with non-foldable queries." I set it up anyway (`RangeStart`/`RangeEnd` as Date/Time parameters, used both in the `sysparm_query` string and in a `Table.SelectRows` step on `sys_created_on`, with "Only refresh complete days" ticked). Settings were: archive 1 year, incrementally refresh last 2 days.

Even with that, refreshes failed. I've since disabled IR entirely to rule it out as the cause, and the timeouts persist — so the bottleneck is the extraction itself, not the partitioning.

**3. Refresh consistently hits the XMLA timeout.** Refresh history shows:

- 3h 25m — Failed

- 4h 23m — Failed

- 5h 0m 5s — Failed (`Data source error: The XML for Analysis request timed out before it was completed. Timeout value: 17999 sec.`)

After four consecutive failures the service auto-disabled scheduled refresh ("Scheduled refresh has been disabled").

**4. Dot-walked reference fields appear to be a major cost.** My incident query requests around 35 fields including several dot-walked ones: `caller_id.u_zone`, `caller_id.u_market`, `caller_id.u_region`, `location.full_name`, `assignment_group.u_stream`. These are business-critical for the dashboard so I can't drop them, but each one forces a reference join server-side in ServiceNow, and I'm also using `sysparm_display_value=true` which resolves every reference to its label. I suspect this combination is where most of the five hours goes.

**5. Malformed rows in the API response.** Occasionally ServiceNow returns an empty string in place of a record inside the `result` array, which breaks `Table.ExpandRecordColumn` with "We cannot convert the value "" to type Record". I've worked around it with `List.Select(..., each Value.Is(_, type record))` before building the table, but flagging it in case others hit the same.

**What I've already tried**

- Moved all dynamic values into the `Query` record so the data source isn't flagged as dynamic

- Added the mandatory `RangeStart`/`RangeEnd` filter step for IR detection

- Ticked "Only refresh complete days"

- Reduced the incremental window to 2 days

- Disabled IR on the small tables

- Locale-safe datetime parsing instead of hard type conversion

- Null-safe filters throughout

None of it got the refresh under the timeout.

**Questions**

Has anyone successfully run incremental refresh against a ServiceNow REST source at this volume? Is there a paging or query pattern that performs meaningfully better than a sequential `List.Generate` loop?
Is there any way to parallelise page requests in Power Query, or is sequential paging an unavoidable ceiling here?
For those who've moved off direct REST extraction — did you go the ServiceNow Database View / scheduled Export Set route, or stage into SQL Server first? Roughly what refresh times did you end up with?
Would a Dataflow Gen1 (Pro licence, no Fabric access) realistically help here, given it decouples the extraction from the dataset refresh window but doesn't make the extraction itself faster?
Any way to raise or work around the 17999-second XMLA timeout on shared capacity, or is that a hard ceiling?

Happy to share the full M script if useful. Any pointers appreciated.

Thanks

Is it possible connect via a guest account to a Delta table in a Lakehouse from another tenant.

FabricEnjoyer — Tue, 15 Sep 2026 11:21:00 GMT

We have the following architecture in Microsoft Fabric:

Open Mirroring Database ↓ Notebook ↓ Materialized Delta Tables (Lakehouse) ↓ Shortcuts into Connection Lakehouse ↓ Power BI Desktop (Azure Data Lake Storage Gen2 connector) ↓ DeltaLake.Table()

Source = AzureStorage.DataLake( "https://onelake.dfs.fabric.microsoft.com/<workspace-id>/<lakehouse-id>/Tables", [HierarchicalNavigation = true] ), dbo = Source{[Name="dbo"]}[Content], TableName = dbo{[Name="<table_name>"]}[Content], Data = DeltaLake.Table(TableName)

What works

Internal users in the hosting tenant can successfully create the connection.
At least one external Entra B2B Guest user can successfully create the connection.
If we create and publish the semantic model ourselves, external customers can copy/use the model successfully.
Existing reports refresh successfully once deployed.

What fails

Several external customer users that have been invited into our tenant as Entra B2B Guests receive a 404 error when attempting to create a new Azure Data Lake Storage Gen2 connection directly from Power BI Desktop.

The users have:

Accepted the guest invitation.
Been granted access to the Fabric workspace(Contributor)
Been granted access to the Lakehouse.
Been added as Guest users in Entra ID.

Observations

The issue is affecting multiple customers, not just a single user.
The same Lakehouse, shortcut tables, and Power Query logic work for other users.
A Guest account from one customer tenant works, while Guest accounts from several other customer tenants receive a 404.
This suggests the issue may be related to cross-tenant authentication, OneLake access resolution, or the ADLS Gen2 connector rather than permissions on the Fabric artifacts themselves.

Questions

Are there known limitations or issues with Azure Data Lake Storage Gen2 connections to OneLake for some Entra B2B Guest users?
Are there specific cross-tenant access settings, trust settings, or Conditional Access configurations that can cause a 404 during OneLake path resolution?
Is there a recommended approach for external customers connecting directly to OneLake Delta tables via the ADLS Gen2 connector?

Any guidance would be appreciated.

Intermittent Power BI Service Refresh Failure with Snowflake – wsarecv Connection Reset

manoj_0911 — Tue, 15 Sep 2026 10:28:53 GMT

Hi everyone,

We are facing an intermittent issue with Power BI Service semantic model refreshes using the native Snowflake connector through an On-premises Data Gateway cluster.

The refresh works successfully in Power BI Desktop, but intermittently fails in Power BI Service.

Error:

DM_GWPipeline_Gateway_MashupDataAccessError [snowflake] Get "https://sfc-oh-ds1-109-customer-stage.s3.us-east-2.amazonaws.com/..." read tcp ...:443: wsarecv: An existing connection was forcibly closed by the remote host

The failure occurs while Power BI is downloading the Snowflake query results from the Snowflake-managed AWS S3 stage. The Snowflake query itself completes successfully.

What we have confirmed

The issue is intermittent.
Retrying the same refresh can succeed without configuration changes.
The issue occurs in Power BI Service but not Power BI Desktop.
We have a Gateway cluster with two nodes, and both nodes have experienced the same issue.
Other data sources using the same Gateway are not affected.
Gateway logs show the connection being reset while accessing the Snowflake S3 stage.
The S3 Stage endpoint is reachable on TCP 443.
Snowflake authentication and query execution are successful.
Microsoft reviewed the Gateway logs and advised that the next investigation should focus on the network path between the Gateway and AWS S3.

Microsoft's latest recommendation is to capture the network traffic during a failed refresh to identify which device is sending the TCP reset. They also recommended checking TLS/SSL inspection, firewall/session timeouts, connection limits, and host-based security agents.

Microsoft recommended testing

netsh trace start capture=yes tracefile=C:\Temp\gw_s3.etl maxSize=2048 report=disabled

Reproduce the failure and then run:

netsh trace stop

They also recommended running:

SELECT SYSTEM$ALLOWLIST();

in Snowflake and reviewing the Snowflake S3 Stage hosts against TLS/SSL inspection and firewall rules.

My questions

Has anyone experienced a similar wsarecv – An existing connection was forcibly closed by the remote host error when refreshing Snowflake data through the Power BI On-premises Data Gateway?

Could this be related to the Gateway's network path to AWS S3 even though TCP 443 connectivity succeeds?
Are there any known Power BI Gateway or Snowflake connector issues that can cause this type of mid-transfer connection reset?
Are there specific Gateway logs or diagnostics that can identify which component initiated the TCP reset?
Has anyone resolved a similar issue by excluding Snowflake S3 Stage endpoints from TLS/SSL inspection?
Are there any recommended tests to distinguish between Gateway, firewall/proxy, endpoint security, and AWS/Snowflake as the source of the reset?

Any guidance or similar experiences would be greatly appreciated.

Thanks!