# Why do I output variable names as numeric values on the command line **URL:** \ **Category:** Programs & Applications\ **Created:** [September 3, 2021, 3:05am UTC](https://forum.dfinity.org/t/why-do-i-output-variable-names-as-numeric-values-on-the-command-line/6937 "2021-09-03T03:05:16Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![eddy](https://avatars.discourse-cdn.com/v4/letter/e/57b2e6/32.png) [@eddy](https://forum.dfinity.org/u/eddy)\ **Post date:** [September 3, 2021, 3:05am UTC](https://forum.dfinity.org/t/why-do-i-output-variable-names-as-numeric-values-on-the-command-line/6937/1 "2021-09-03T03:05:16Z")
![image](https://us1.discourse-cdn.com/flex023/uploads/dfn/original/2X/e/e8b3202f7873747017de5d00a850a0f82091c255.jpeg) ---
**Author:** ![nomeata](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/nomeata/32/733_2.png) [@nomeata](https://forum.dfinity.org/u/nomeata)\ **Post date:** [September 3, 2021, 10:19am UTC](https://forum.dfinity.org/t/why-do-i-output-variable-names-as-numeric-values-on-the-command-line/6937/2 "2021-09-03T10:19:14Z")
The Candid wire format does not transmit full field names, but only hashes. In most cases the receiver knows which field names to expect (e.g. a Motoko service), and things work. But in dynamic use, e.g. `dfx` printing Candid value without knowing the expected type, it can’t do much better than printing the hash. Maybe future versions will be able to fetch the interface to help here, or maybe Candid will change to include the actual field names. ---
**Author:** ![nomeata](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/nomeata/32/733_2.png) [@nomeata](https://forum.dfinity.org/u/nomeata)\ **Post date:** [September 3, 2021, 10:20am UTC](https://forum.dfinity.org/t/why-do-i-output-variable-names-as-numeric-values-on-the-command-line/6937/3 "2021-09-03T10:20:49Z")
Actually, in your case (dfx talking to a local, named Rust cansiter) it should suffice to include the did file in dfx.json, I believe.