In a discovery pattern, a custom field is correctly found, but is not included in "CI creating"

[Cedric Creton]

Dear community,

I created a discovery extension that is working fine (check wether or not a win server has NFS services installed, and filling a custom field ((added in cmdb_ci_server )).

It was working file in DEV & TST, but I made some mix/mess when deploying in PRD with form layouts.

And now you can see it's not oncluded in the "CI Creating" phase.

I got it already and reviewed on the affected instance formlayouts=> it solved the issue).

Now I have again the issue and trying to correct it by the right way.

--New Update set in DEV

-Using "from design" removing the field and saving

-Re-adding the field and saving

--Commit update in TEST:

-test OK

--Commit update in PRd:

-test failing (see picures)

What's wrong? How to reveiw/force that to be used in CI Creation?

Many thanks for your advices!!

[Venky VA]

make sure newly added field is present in CI table and same name used in extension to fill the value.

[Ivar Donado]

I am going through the same. I added an extension to the Windows - Desktop OS pattern to map some data to a custom field. It did work in DEV, but the custom field never showed in the "Creating CI" phase of discovery. The name is correct.

[danielkillian]

Hey Guys,
I have the same issue. Any idea ?