I did it at first, which left me with some missing values where the "X" has been, still the view did not pick up the data and the same error...

Thank you.

I ran the execute step in SQL. It does not do what its suppose to do. I included all the relevant codes with sample data.

Due to security i could not export data from the particular DB. I imported the very same flat files into my personal DB , with no issue. YOU could have...

I have made it very easy, gave data in more than one format. Its you guys that makes it difficult. Your all full of nonsense! What more do you expect...

The data is attached as previously discussed. I also included the DDL's of all the tables, to make it easy to recreate and insert data. Data is available in bacpac.

• This reply was modified 5 months, 1 week ago by  yrstruly.
• This reply was modified 5 months, 1 week ago by  yrstruly.

Codes below are for the Updated Table:

USE [IMETA_FINAL]

GO

/****** Object:  Table [Prod].[IMETA - Calendar Days Data_Table_Other]    Script Date: 7/16/2024 5:22:54 PM ******/SET ANSI_NULLS ON

GO

SET QUOTED_IDENTIFIER ON

GO

CREATE TABLE [Prod].[IMETA - Calendar Days...

• This reply was modified 5 months, 1 week ago by  yrstruly.
• This reply was modified 5 months, 1 week ago by  yrstruly.

The code below gets data for FY 2025. Now its a matter of altering the main code to get desired data set. I have made a whole set of data...

• This reply was modified 5 months, 1 week ago by  yrstruly.
• This reply was modified 5 months, 1 week ago by  yrstruly.

Code:

-- Define fiscal year periods with their corresponding start and end dates

WITH FiscalCalendar AS (

SELECT 'FY25' AS FY, 'P1' AS Period, '2024-07-01' AS PeriodStart, '2024-08-03' AS PeriodEnd UNION ALL

SELECT 'FY25',...

Here is the other table that is joined:

• This reply was modified 5 months, 1 week ago by  yrstruly.

The latest financial year is 2025. The new table has data for 2025. Like I said, I used the Orinal table and updated with data of 2025 and the code...

• This reply was modified 5 months, 1 week ago by  yrstruly.

SET DATEFIRST 7; -- Holding Period QuerySELECT WEEK_NUMBER.[Week Number], WM_GH.[Calendar day], WM_GH.[Month/Week], WM_GH.[Day name], WM_GH.[Company], WM_GH.[Material Code], WM_GH.[Metric], WM_GH.[Metric Value]FROM ( SELECT [Calendar day], [Month/Week], [Day name], [Company], [Material Code],...

Attached is some sample data. I could get this code to work, by inserting one row where FY/YEAR is 2024 and all of FY/YEAR 2025.

The original tables data goes up...

• This reply was modified 5 months, 1 week ago by  yrstruly.

I found a code that works:

#region Help: Introduction to the script task
/* The Script Task allows you to perform virtually any operation that can be accomplished in...

• This reply was modified 9 months, 1 week ago by  yrstruly.
• This reply was modified 9 months, 1 week ago by  yrstruly.

I tested the C# code/ ran it i cant close the script editor because the error is there. I also resolved this: