The workflow relies on the buildingSMART IDS standard , ensuring compatibility across different software vendors.
Sophisticated malware uses "VBA Stomping" (also known as VBA Purge). The attacker removes the parsed VBA code (the ProjectStream ) but leaves the unparsed source code ( CompressedSourceCode ). Most antivirus scans the ProjectStream , finding nothing. IDSxls allows you to view the raw streams directly. If you see a CompressedSourceCode stream but no ProjectStream , you have identified stomped macros. idsxls work
Spreadsheets lack the built-in validation of a dedicated IDS editor, meaning errors in the Excel file may only be caught during the conversion or audit phase. 5. Conclusion The workflow relies on the buildingSMART IDS standard
| Symptom | Likely Root Cause | Solution | |---------|------------------|----------| | File not detected | Incorrect folder permissions or file naming convention | Verify the IDS service account has read access. Ensure file names match regex pattern (e.g., orders_*.xlsx ) | | Wrong data in target | Column mismatch or header row changed | Compare source Excel header row to expected schema. Lock template cells. | | Slow processing | Excessive formatting, large images, or 100,000+ rows within Excel | Convert source to XLSX (not legacy XLS). Use CSV as an intermediate format. Implement pagination. | | Special characters garbled | Encoding mismatch (UTF-8 vs. ANSI) | Force Excel to save as UTF-16 or configure IDS to handle Windows-1252 encoding | | Duplicate records | No idempotency check | Add a unique constraint check (e.g., composite key of date + invoice number) before insert | Most antivirus scans the ProjectStream , finding nothing