I am trying to retrieve Apex classes or anything from sandbox Org to my local system with VS code then I am getting follwoing error
Unexpected child metadata [\force-app\main\default\objectTranslations\SomeObjectNameHere-en_US\parent_account.fieldTranslation-meta.xml] found for parent type [CustomObjectTranslation]
I started getting this error when I tried to retrieve custom object translation into local system then I tried to retrieve another thing also getting same errors,Can you please help me to resolve this error.
I faced a same issue and resolved it recently. The only difference was in my case it was a deploy and and in your case its a retrieve. May be this could solve your issue
The xxx.objectTransalation-meta.xml file was not present due to which it was throwing an error. Create a file give the exact name(Transalation Object Name) to it. This should resolve the error
Please refer to below snapshot
https://i.stack.imgur.com/eoB3Q.png)
Related
On loading react application it is rendering perfect but only for a few sec. after that it shows this error. unable to debug this. Showing error in node_modules/react-dom/cjs/react-dom.development.js:21959
Can anyne help me with this?
don't manipulate data directly first make copy then modify it
I was trying to set up a watson studio , but I keep getting error message that says 'can not read property 'language_info' undefined'
Same issue for a course project. No one else has seemed to encounter it.
I changed the URL I was using to http from https and it worked. This could be the solution, or I just needed to back up and try it again.
In case it saves someone a bit of time:
I ran into the same issue in the Assignment 2 of the class "Fundamentals of Scalable Data Science". The reason is that the URL we had to import as Notebook is not the first one that appears in the instructions, as it was in Assignment 1. The URL to be imported was lower on the page.
Long story short: You may be importing the wrong URL.
My adaljs code to fetch a token for a web api is suddenly failing. This has been working for months now. Since yesterday, I get the following error.
Invalid_state. state: 7ea40a81-5491-47a1-8ebc-89488acb673a|https://sykesenterprises.onmicrosoft.com/MyAPI
This happens when the acquireToken method is called.
I am using the example from https://blog.mastykarz.nl/building-office-365-web-applications-react/ to use react with adaljs.
Managed to sort this out. If anyone else has the same issue, the answer was to just call adal.handleWindowCallback() at the entry point to the application.
The issue occurs because the sample you are referring to needs to be updated as per the latest version of Adal 1.0.16. I was able to fork the repo and submit a pull request to the owner to fix the invalid_state issue. Please refer to the link below to see the code changes:
https://github.com/waldekmastykarz/office-mygroups-react/pull/3/files
Google Drive Realtime API has a nice set of errorTypes that you can listen for, so you can handle each case individually:
https://developers.google.com/drive/realtime/reference/gapi.drive.realtime.ErrorType
Unfortunately, this list doesn't include the DocumentClosed error. For some reason, that error is its own object in the API.
https://developers.google.com/drive/realtime/reference/gapi.drive.realtime.DocumentClosedError
For the life of me, I cannot figure out how to handle this error. I have an onError listener function set up on my realtime.load, but that only catches Errors, which are different than the DocumentClosedError.
Is there any way to handle/listen for this particular type of error? I have also tried document.addEventListener but that was a desperate attempt and didn't work
For anyone else wondering about this, it was related to binding between angular and google drive.
The document was closed for google but the angular binding were still there.
We handled this by intercepting the angular error based on this.
http://odetocode.com/blogs/scott/archive/2014/04/21/better-error-handling-in-angularjs.aspx
The DocumentClosedError is a different type of error as it is only thrown when you are accessing an invalid document. The only times that that Realtime Document should be invalid are: 1) after one of the fatal errors defined in ErrorType is handled by your error function, or 2)after you call .close() yourself on the document.
Tracking whether you hit one of these two conditions on the client and ensuring you don't access the Document afterwards is how to prevent the error from firing. Ideally if you get into a state where your document is closed, the app should teardown its references to the realtime models and reconnect to reduce the number places that you will throw exceptions.
TL;DR: If you're hitting DocumentClosedErrors you should change the way that you handle fatal errors defined in ErrorType.
Iam trying to store the state in thedb through webservice.
Iam using Http State Provider to do so.
Iam getting an error in the following line saying object expected.
Ext.state.Manager.setProvider(new Ext.state.HttpProvider({ url: 'GetGridState.asmx/readdata' }));
Please help me in this issue.
You should probably use firebug or even alerts if nothing else to see if maybe you're not passing an object where you should be.
Are you using the correct version of ExtJS? It looks like there is no more Ext.state.HttpProvider in ExtJS 3.1.
Sounds like you have not included the HttpStateProvider class code correctly, or included it after the code that is trying to use it. Double-check that if you are referring to an external js file, it is loaded properly and in the right order.