The computed property "fields" is already defined as a prop. about vue-json-excel

[niravshah]

For me this was happening because I was using vee-validate. You can configure vee-validate to use a different name for the fieldsbag using the below syntax

Vue.use(VeeValidate, {
   fieldsBagName: 'vvFields'
});

[jecovier]

hey guys, I see this is a frequent problem so I made a little change that don't breaks backward compatibility. "fields" is no longer a required prop and you can use either "fields", "export-fields" or "exportFields" to define the data you want to export. I hope this fix this issue, let me know otherwise. thank you for your help

[imsyuan]

hey guys, I see this is a frequent problem so I made a little change that don't breaks backward compatibility. "fields" is no longer a required prop and you can use either "fields", "export-fields" or "exportFields" to define the data you want to export. I hope this fix this issue, let me know otherwise. thank you for your help

Hi, I replace "fields" with "export-fields" or "exportFields" but I still get the same error message.

Here is the solution for me.

import Vue from 'vue'
import VeeValidate from 'vee-validate'

Vue.use(VeeValidate, {
  inject: true,
  fieldsBagName: 'veeFields'
});

bootstrap-vue/bootstrap-vue#1270 (comment)

[Jeffrey-Kimani]

Same issue here mine doesn't even download the file on chrome

[paaysay]

I am also facing the same issue. Whats the solution for this?

[jombard]

I think there is a conflict with another component here. When I change the fields prop name to something else I don't get the warning. This would probably be a breaking change so not sure how to proceed. Any ideas?

[abnerwang0991]

I am also facing the same issue.
I guess the problem is caused by vee-validator, becuase it has 'fields' property.

[pudjamansyurin]

same with me, no solution yet?

[pudjamansyurin]

the solution for me, just hack the core, then find keyword 'fields' replace it to anything you want, ex 'json_fields'

[higbdesign]

hey guys, I see this is a frequent problem so I made a little change that don't breaks backward compatibility. "fields" is no longer a required prop and you can use either "fields", "export-fields" or "exportFields" to define the data you want to export. I hope this fix this issue, let me know otherwise. thank you for your help

Hi,
if I don't want to set the field prop (because I want export all the fields) how can I change the prop name?

[MOHAMMED-ABD-RAZAQ]

was useful thanks

[juanlopezdev]

hey guys, I see this is a frequent problem so I made a little change that don't breaks backward compatibility. "fields" is no longer a required prop and you can use either "fields", "export-fields" or "exportFields" to define the data you want to export. I hope this fix this issue, let me know otherwise. thank you for your help

Hi, I replace "fields" with "export-fields" or "exportFields" but I still get the same error message.