Invoke-PnPSiteTemplate -Handler Fields Creates subweb fields with existing rootweb field properties

[diegolonghi]

I'm working with SharePoint Online, considering the structure
Site
|-RootWeb
|--Site Field - "Alpha" - ID: 123 - StaticName "Alpha" - InternalName "Alpha"
|-Subweb
|---Site Field - "Beta" - ID: 123 - StaticName "Alpha" - InternalName "Alpha"
|---Content Type - "X"
|--- FieldRef - "Beta" - ID: 123
|---ListInstance
|----Content Type - "XX"
|----FieldRef - "Beta" - ID:123

Editing the the rootweb site field OR subweb site field afects the list instance field and both (field "Beta" and field "Alpha") have they removal blocked by beeing used but they are diferent objects that do not have a relationship.

I didn't expect the provision tool could create a field at subweb level using the same ID, InternalName and StaticName that already exists on rootweb and I don't remember this behaviour happening on premises.

I expected the provisioning tool to check the web available columns before adding it.
Is this an expected behaviour?

[diegolonghi]

I'm investigating this case... found out that an exception is thrown but the fields are created/overwritten (if already exists), this is probably a server side bug. I'm looking at the PNP code to report this issue at the server api. The whole structure references are a mess now, duplicate fields (ID, internal name), wrong parent/child fields sync, wrong deletion locks.