Tools 10.5 - Attribute By Key Values - Fails to produce changes

[rbeard09]

When the Attribute By Key Values tool is run it quickly declares itself completed however no changes have occurred.

I have attached a screenshot of the ArcDesktop Output and the formatted text file.

This tool does function using the ArcPro tools using the same in puts.

Not everyone here is in Pro so I need to figure out how to make the tool work.

DigAtlas250K_KeyValues.txt

[ethoms-usgs]

With no error message, that's hard to troubleshoot. I don't have a working version of ArcMap running at the moment, so I can't check much.

This is a slightly kludgy way to go about this but I have attached three previously committed versions of that script. Try each one behind the parameter form or from the command line and see if one works. Then we can track down the changes. You will have to rename the files with a .py extension.

keypairs_dec18.txt
keypairs_nov18.txt
keypairs_dec17.txt

You can also get to these yourself. At the main repo page, go into Scripts, click on the script, and on the next page click 'History'. You get a list of the times when changes were made to the script and uploaded here. Go to the <> icon for any one of those to 'Browse the repository at this point in the history'. Navigate back to the script page where you can see the contents of the script file and click 'Raw'. Copy all of the text you see on the next browser page and paste it into a text file naming it whatever you like with a .py extension.

[rbeard09]

Hello,

This morning I tried all three versions of the tool.

The _dec17 version worked!! It ran for more the .01 seconds and populated the fields according to the input text file.

It appears that this version does not overwrite existing values? And that is what the subsequent tools were trying to do?

Thank you for your support on this.

[ethoms-usgs]

Good! That's something.

Yes, this version only calculates only on rows where Type is NULL.

The versions that supersede this one were edited to find feature classes in feature datasets in addition to GeologicMap. I didn't write those, but looking at the code, I don't see a problem with it. I will take a closer look when I have ArcMap running again.

[rhaugerud]

I recently discovered that, in ArcMap, the tool ran quite happily and declared that it was working. Upon completion, the gdb showed no changes!

Then I ran it while editing the gdb and the changes stuck.