Is the new ArcGIS Pro 3.6 model builder completely broken?

[DuncanHornby]

Hi Community,

Is it me or is the new ArcGIS Pro 3.6 model builder broken? It appears any tool that has a filter parameter or field map is unable to see any previous additional fields. See my video below. All I do is add a field, calculate a value into it then attempt to view that field I just added. I have restarted ArcPro, started with a blank project and tried different datasets (all file geodatabases on c:\) and tools (e.g. Make FeatureLayer) and I can replicate this issue. It makes model builder and any bespoke python tool developments unusable! This is a MAJOR problem. Unless I'm doing something wrong, happy for anyone to shoot me down in flames as I need modelbuilder to be working!

See how the filter and field maps do not work

Tagging: @ShitijMehta , @KoryKramer 

[LindsayRaabe_FPCWA]

Geez.... hope you're doing something wrong (though I can't see what it would be) as I'm hoping that upgrading to 3.6 would fix this Bug! Will definitely hold out and wait to see what you determine. Seems like a pretty big downgrade if it's intentional. 

[RyanUthoff]

I can confirm this behavior in Pro 3.6 on my test machine, but I can also confirm this same behavior in Pro 3.2. The only way I can get the new field to appear is to partially run the model in ModelBuilder first (up to the point where the new fields are missing). Then after running the tools, the new fields are visible for me to be able to select.

Ideally, it would be nice for the new fields to be visible downstream without having to partially run the model first. We replaced ModelBuilder with FME years ago, so I can't remember if it's always been that way or not.

[ShitijMehta]

@DuncanHornby 
We have a bug with Export feature slated to be fixed for 3.7. I am truly sorry for this issue with the tool (not ModelBuilder). Will update as soon as it is fixed. Sorry once again! 

[DuncanHornby]

@ShitijMehta nothing to be sorry about I'm just pleased to see that you are working on a fix! I should say that I don't think this issue is specific to the export tool, I had the same issues with the Make Feature Layer tool, which makes me think its a wider issue for tools that have parameters that are filters or have fieldmaps. I stumbled across this issue which made me then "go to the basics" as shown in the video above not because of using model builder but I was testing my python tools that add additional fields to the schema for an output parameter so they can be used in model builder, that's when I spotted the issue (because it all failed). My python tools did not have this problem in 3.5. I hope that's an additional nugget of information for your team...

[ShitijMehta]

@DuncanHornby Thank you for mentioning MFL tool as well. Well test and try to resolve this.