Power BI is turning 10! Tune in for a special live episode on July 24 with behind-the-scenes stories, product evolution highlights, and a sneak peek at what’s in store for the future.
Save the dateEnhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.
Hi Folks,
I have created this query in snowflake to convert JSON format data into table structure:
select *, doc:"_class"::STRING AS Class,
doc:"_id"::STRING AS Id,
doc:"mvrId"::STRING AS mvr_id,
doc:"orderNumber"::STRING AS Order_Number,
doc:driverLicenseRecord:record:dlRecord:criteria:firstName::STRING AS criteria_First_Name,
doc:driverLicenseRecord:record:dlRecord:criteria:host::STRING AS criteria_Host,
doc:driverLicenseRecord:record:dlRecord:criteria:lastName::STRING AS criteria_Last_Name,
doc:driverLicenseRecord:record:dlRecord:criteria:licenseNumber::STRING AS criteria_license_Number,
doc:driverLicenseRecord:record:dlRecord:criteria:accountId::STRING AS criteria_Account_Id,
doc:driverLicenseRecord:record:dlRecord:criteria:birthDate:full::DATE AS criteria_Birth_Date,
doc:driverLicenseRecord:record:dlRecord:criteria:orderDate:full::DATE AS criteria_Order_Date,
doc:driverLicenseRecord:record:dlRecord:criteria:productID::STRING AS criteria_Product_ID,
doc:driverLicenseRecord:record:dlRecord:criteria:reference::STRING AS criteria_Reference,
doc:driverLicenseRecord:record:dlRecord:criteria:routing::STRING AS criteria_Routing,
doc:driverLicenseRecord:record:dlRecord:criteria:state:full::STRING AS criteria_State_Full,
doc:driverLicenseRecord:record:dlRecord:criteria:subtype::STRING AS criteria_Sub_type,
doc:driverLicenseRecord:record:dlRecord:criteria:subtypeFull::STRING AS criteria_Subtype_Full,
doc:driverLicenseRecord:record:dlRecord:criteria:trackingNumber::STRING AS criteria_Tracking_Number,
doc:driverLicenseRecord:record:dlRecord:currentLicense:licenseInformation:classCode::STRING AS currentLicense_Class_Code,
doc:driverLicenseRecord:record:dlRecord:currentLicense:licenseInformation:classDescription::STRING AS currentLicense_Class_Description,
doc:driverLicenseRecord:record:dlRecord:currentLicense:licenseInformation:type::STRING AS currentLicense_Type_List,
doc:driverLicenseRecord:record:dlRecord:currentLicense:number::STRING AS currentLicense_Number,
doc:driverLicenseRecord:record:dlRecord:driver:age::STRING AS driver_Age,
doc:driverLicenseRecord:record:dlRecord:driver:birthDate:full::DATE AS driver_Birth_Date,
doc:driverLicenseRecord:record:dlRecord:driver:firstName::STRING AS driver_First_Name,
doc:driverLicenseRecord:record:dlRecord:driver:gender::STRING AS driver_Gender,
doc:driverLicenseRecord:record:dlRecord:driver:height::NUMBER AS driver_Height,
doc:driverLicenseRecord:record:dlRecord:driver:lastName::STRING AS driver_Last_Name,
doc:driverLicenseRecord:record:dlRecord:driver:eyeColor::STRING AS driver_Eye_Color,
doc:driverLicenseRecord:record:dlRecord:driver:hairColor::STRING AS driver_Hair_Color,
doc:driverLicenseRecord:record:dlRecord:driver:weight::NUMBER AS driver_Weight,
doc:driverLicenseRecord:record:dlRecord:currentLicense:licenseInformation:expirationDate:full::STRING AS currentLicense_Expiration_Date,
doc:driverLicenseRecord:record:dlRecord:currentLicense:licenseInformation:issueDate:full::STRING AS currentLicense_Issue_Date,
doc:driverLicenseRecord:record:dlRecord:result:control::STRING AS result_Control_List,
doc:driverLicenseRecord:record:dlRecord:result:returnedDate:full::DATE AS result_Returned_Date,
doc:driverLicenseRecord:record:dlRecord:result:valid::STRING AS result_Valid_List,
Address_List.value:"City"::STRING AS AddressList_City_List,
Address_List.value:"County"::STRING AS AddressList_County_List,
Address_List.value:"State":Full::STRING AS AddressList_StateFull_List,
Address_List.value:"Street"::STRING AS AddressList_Street_List,
Address_List.value:"Zip"::STRING AS AddressList_Zip_List,
Message_List.value:"line"::STRING AS Message_Line_List,
Event_List.value:"Common":Date:Full::DATE AS EventList_Common_Date,
Event_List.value:"Common":PostedDate:Full::STRING AS EventList_Posted_Date,
Event_List.value:"Common":IsCommercial::STRING AS EventList_IsCommercial_List,
Event_List.value:"Common":IsHazMat::STRING AS EventList_IsHazMat_List,
Event_List.value:"Common":State:Full::STRING AS EventList_StateFull_List,
Event_List.value:"Common":Type::STRING AS EventList_Type_List,
Event_List.value:"Common":Subtype::STRING AS EventList_SubType_List,
Event_List.value:"Violation":ConvictionDate:Full::DATE AS Violation_Date,
Event_List.value:"Action":ClearDate:Full::Date AS action_Clear_Date,
Event_List.value:"Action":MailDate:Full::STRING AS action_Mail_Date,
Description_List.value:"Acd"::STRING AS Acd_List,
Description_List.value:"AdrLargeDescription"::STRING AS AdrLarge_Description_List,
Description_List.value:"AdrSmallDescription"::STRING AS AdrSmall_Description_List,
Description_List.value:"Avd1"::STRING AS Avd1_List,
Description_List.value:"Avd2"::STRING AS Avd2_List,
Description_List.value:"Avd3"::STRING AS Avd3_List,
Description_List.value:"StateAssignedPoints"::STRING AS State_Assigned_Points_List,
Description_List.value:"StateCode"::STRING AS State_Code_List,
Description_List.value:"StateDescription"::STRING AS State_Description_List,
Description_List.value:"TableKey"::STRING AS Table_Key_List
from (
select parse_json("_doc") as doc from "AIGI_EDR_REPLICATEDDATA"."LOSS_SENSITIVE_DEV_DATA"."mvr_db_driver_license_record"),
LATERAL FLATTEN(input => doc:driverLicenseRecord:record:dlRecord:driver:addressList) AS Address_List,
LATERAL FLATTEN(input => doc:driverLicenseRecord:record:dlRecord:messageList) AS Message_List,
LATERAL FLATTEN(input => doc:driverLicenseRecord:record:dlRecord:eventList) AS Event_List,
LATERAL FLATTEN(input => Event_List.value:"DescriptionList") AS Description_List;
when use Snowflake as my data source and put this query into SQL Native query and used Direct query mode.
I am getting this error:
Expression.Error: The field 'SEQ' already exists in the record.
Could you please help me to resolve this issue?
Regards,
Ranjeet Jha
Solved! Go to Solution.
Hi @BI_Master123.,
Thanks for reaching MS Fabric community support.
The error Expression.Error: The field 'SEQ' already exists in the record arises because the field SEQ is being introduced multiple times in the query, possibly due to it being present in both the main JSON object and within one or more nested arrays (such as in the Address_List, Event_List, or other flattened structures).
The SEQ field is likely appearing in both the main document (doc) and within the arrays being flattened (Event_List, Address_List, etc.), causing Snowflake to throw a conflict when creating the result set.
Please let me know if this helps resolve your query?
Thanks,
Prashanth Are
MS Fabric community support
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly and give Kudos if helped you resolve your query
@BI_Master123, As we haven’t heard back from you, we wanted to kindly follow up to check if the solution provided for your issue worked? or let us know if you need any further assistance here?
Thanks,
Prashanth Are
MS Fabric community support
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly and give Kudos if helped you resolve your query
@BI_Master123, As we haven’t heard back from you, we wanted to kindly follow up to check if the solution provided for your issue worked? or let us know if you need any further assistance here?
Thanks,
Prashanth Are
MS Fabric community support
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly and give Kudos if helped you resolve your query
@BI_Master123, As we haven’t heard back from you, we wanted to kindly follow up to check if the solution provided for your issue worked? or let us know if you need any further assistance here?
Thanks,
Prashanth Are
MS Fabric community support
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly and give Kudos if helped you resolve your query
Hi @BI_Master123.,
Thanks for reaching MS Fabric community support.
The error Expression.Error: The field 'SEQ' already exists in the record arises because the field SEQ is being introduced multiple times in the query, possibly due to it being present in both the main JSON object and within one or more nested arrays (such as in the Address_List, Event_List, or other flattened structures).
The SEQ field is likely appearing in both the main document (doc) and within the arrays being flattened (Event_List, Address_List, etc.), causing Snowflake to throw a conflict when creating the result set.
Please let me know if this helps resolve your query?
Thanks,
Prashanth Are
MS Fabric community support
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly and give Kudos if helped you resolve your query
Check out the July 2025 Power BI update to learn about new features.
This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.