Can't export Tables

Are you looking for help?

This is a support forum for reporting issues related to Backendless services. Please note that due to our support policy we cannot provide you help with debugging your code, consulting in regards to any language or third-party library usage. For this kind of questions we recommend using more appropriate forums like Stack Overflow.

In order to suggest you a quality solution, we shall usually ask you to provide the details mentioned below first. Including them into your topic right away helps us to start investigating your issue much faster.

In case you have a suggestion or an idea, the details below are not always required, though still any additional background is welcome.

Backendless Version (3.x / 6.x, Online / Managed / Pro )

6.x

Client SDK (REST / Android / Objective-C / Swift / JS )

Application ID

8C44389D-54B2-5DF3-FFF8-40A831D81800

Expected Behavior

Please describe the expected behavior of the issue, starting from the first action.

  1. I can’t. export Tables from the Console

Actual Behavior

Please provide a description of what actually happens, working from the same starting point.

Be descriptive: “it doesn’t work” does not describe what the behavior actually is – instead, say “the request returns a 400 error with message XXX”. Copy and paste your logs, and include any URLs.

  1. Here is the error
    Backendless finished export your data unsuccessfully for application: leet.

See export log bellow:

1 11:06:35 EXPORT Export started
2 11:06:35 EXPORT Exporting table: beEvents
3 11:06:36 EXPORT Generating export.zip
4 11:06:36 EXPORT Uploading export.zip to File Service
5 11:06:36 EXPORT Export failed No enum constant com.backendless.billing.BillingPlan.
2.
3.

Reproducible Test Case

Please provide a simple code that could be run in a new clean app and reproduce the issue.

If the issue is more complex or requires configuration, please provide a link to a project on Github that reproduces the issue.

Hi @eyad-pro,

thanks for reporting this issue! I was able to reproduce that, internal ticket has been created and issue will be fixed asap. You can reference the issue by it’s ID - BKNDLSS-21998.

We’ll let you know once it fixed. Please stay tuned and sorry for the inconvenience.

Regards,
Stanislaw

Hello @eyad-pro

Please check now.
Please, write about the result.

Thanks … working now