I have a back4app parse database that has a class containing images. I need to import this class into another back4app parse database. When I export it to json and attempt to import it, I get the following: This XML file does not appear to have any style information associated with it. The document tree is shown below. Followed by an error stating access denied. What do I need to do to get this to work?
To clarify the solution: the files must be cloned into the new database, which can only be done by contacting back4app directly and asking them to do it.
I recommend that you sent a email or talk at chat with Back4App, the error that you reported is necessary clone your files/images.
Related
I have a piece of file access code which uses FSGetCatalogInfo to get info about a bundle (say .xyz) which itself contains a file with extension .xyz. Because FSGetCatalogInfo has been updated, I am looking to replace it with 'getResourceValue' API from Foundation layer. However, the OSType is coming incorrect from the new API.
I have also looked into the related FSSetCatalogInfo API. Do I need to do something equivalent such that the 'getResourceValue' API will start giving correct results?
Hi exported my app before parse.com was shutdown and I saw some JSONs so i though it is OK. Today I tried to import these data to mongo only to find out that I need _Schema file import too but it is missing from the exported file.
Is there a way how to generate this file?
Looking at the _SCHEMA collection of my local Parse Server installation it seems fairly easy to reconstruct manually. It only contains the columns and their types for each collection with the collection name being the object id.
Below is an example of the _SCHEMA entry for my _User collection
I created a dashboard in pentaho CDE with some title and description.
Now when I call the api "pentaho/api/repo/files/[Path]/children?showHidden=false&filter=*.wcdf", I am getting file list with properties.
However, if I change the properties like title / description, and save the dashboard those changes are not getting reflected.
Also when I export these files and import into another folder, the description property is not coming in the api call.
What could be the reason and how to solve this?
We are collaborators on a Parse.com App and we need to recreate the App in another account as we are ending our relationship with the original App creators.
We have copied all the classes and exported all the data from the previous App but are getting errors with the JavaSript API (Access Denied/403 issue). Has anyone else experienced this? What did you do to overcome the problem?
Thanks!
The Parse.com dashboard has export to JSON which you can then import from the data browser on your second app.
Object IDs will not be preserved.
One big thing to be aware of:
Any referenced PFFiles are NOT exported, so all the references in your rows are not valid, as the new database is not part of the ACL of the old PFFiles.
Either export+import the PFFiles manually, or change the ACLs, if that is indeed possible.
when trying to import customizations for a specific entity I get an error saying that I can't reuse system queries for a custom entity.
The error in the title appears in the detailed CRM trace:
Could not import a Saved Query {C9771189-0CB3-E111-A93D-00505699001D} for ObjectTypeCode 10010 because this is a system Saved Query. The Entity you are trying to import is not the same as the one existing in the database even though it has the same name.
the id of the query is the one in the source customizations.
Both the source and target entities seem to have the exact same queries, with the same names.
Google hasn't been able to offer much on this.
Can anyone shed any light on the subject?
Is your source environment upgraded from v3.0? If so have you applied the hotfix (or latest rollup) mentioned in this KB article to both servers?