BIS import/export template from Sage passed on SEED but failed on Production

SOLVED

Hi,

I need advice and pointers to identify the root cause of the import failure issue.

Sage X3: v12 Patch 31 (latest patch by time of writing)
Database: SQL Server 2019 Standard
All components are updated to match Sage X3 v12p31 requirements.

On SEED folder, using BIS import/export template (Owner: SAGEDEFAULT), no issue:

On a production dummy folder, using BIS import/export template (Owner: SAGEDEFAULT):

```

------------------- Record No. 1 (Line Number 1)

Field DUDDAT (  /  /  ) : Mandatory field

1 records rejected

```


The error is immediate. If I use Test:

As a proof it is Sage X3 v12p31:


For context, assume:
1. Production dummy folder is converted from Sage X3 v11 instance.
1.1. Note that the BIS import/export works fine for production dummy folder in Sage X3 v11 instance.
2. When I check the production folder, in TRT folder, there are 62,000+ files.
3. This production folder is passed down to me with no prior documentation. Client was also kept in the dark and have no documentation about the implementation as well.
4. There were few customized legislations in-place. I cannot delete them.


Few things confirmed:
1. File format is not an issue (Delimited or XML is not an issue).
2. Folder parameters are not an issue. My team has ascertained all the parameters are carried over safely.
3. A folder validation (from X3 to the production dummy folder), entry transaction validation, and archive generation (from X3 to the production dummy folder) have been done.
4. I believe legislation is not the issue. My team done a full dummy company setup dedicated to using BRI legislation and it still got error.