Skip to content

Consistent Field Renumbering Implementation#132

Open
metda11 wants to merge 1 commit intoBartPermentier:masterfrom
metda11:renumberFields-Consistent
Open

Consistent Field Renumbering Implementation#132
metda11 wants to merge 1 commit intoBartPermentier:masterfrom
metda11:renumberFields-Consistent

Conversation

@metda11
Copy link

@metda11 metda11 commented May 21, 2025

Overview

This pull request implements a new feature to consistently renumber fields across AL objects (tables and table extensions) while maintaining field number relationships between different objects. Especially importend when Transferfields are used!

@dsaveyn
Copy link
Collaborator

dsaveyn commented Jul 11, 2025

@metda11 Thank you so much for the contribution an our apologies for the delay.

So if I get the code correctly here's the difference between the current functionality and the suggested one:

Old behavior (processes each file independently):

File1: field(500) → field(100), field(501) → field(101), field(502) → field(102)
File2: field(500) → field(100), field(503) → field(101), field(504) → field(102)

New behavior (uses global mapping):

File1: field(500) → field(100), field(501) → field(101), field(502) → field(102)
File2: field(500) → field(100), field(503) → field(103), field(504) → field(104)

Correct?

@metda11
Copy link
Author

metda11 commented Jul 24, 2025

@dsaveyn, yeah that looks great!, The important thing is that the transferfield functionality still works properly!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants