In Release 5.3 While Creating Transfer Orders automatically (Replenishment to a Transfer Warehouse), the list gets generated but processing gives an error:
Company ID : ### (Branch ID giving the BAccountID ) is not found for
Warehouse ### !
Is there any simple update way to resolve this in v5.3? I did not get this error in release v6.1
Related
I am running catalog synchronization with products, category etc. However, I can see too many logs with the following info:
INFO [SyncWorker<000000S8 2 of 8>] [AbstractItemCopyContext] cannot create item due to pending attributes (..nonmandotory attributes)
INFO [SyncWorker<000000S8 3 of 8>] [AbstractItemCopyContext] cannot create item due to pending attributes (..nonmandotory attributes)
The sync is successful, but takes a lot of time to complete. The reason for this log is in ItemCreator.java:
if (cannotCreate) {
throw new ItemCopyCreator.MissingInitialAttributes("cannot create item due to pending attributes (values " + this.getCopyContext().valuesToString(initialValues) + ")", this._sourceItem);
}
This flag is true for all mandatory fields as per my understanding, hence would be called for baseproduct attribute also(logged when base product is picked up).
Any inputs on how to avoid this scenario? Can this be the reason for slow sync? Query time looks normal as per jdbc logs
I'm trying to use Apple's CoreDataCloudkitDemo app. I've only changed the app settings per their README document. On running the demo, I'm getting the error: "CloudKit integration requires does not support ordered relationships."
(The weird grammar in the title is included in the app)
The console log shows:
Fatal error: ###persistentContainer: Failed to load persistent stores:Error Domain=NSCocoaErrorDomain Code=134060 "A Core Data error occurred." UserInfo={NSLocalizedFailureReason=CloudKit integration requires does not support ordered relationships. The following relationships are marked ordered:
Post: attachments
There is the same error for the "Tags" entity.
I'm using Xcode 11.0 beta 4 (11M374r).
I've only changed the bundle identifier, and set my Team Id.
I removed the original entitlements file - no errors in resulting build.
I've not changed any code from the original.
Does anyone have a workaround, or preferably, a fix? Or did I do something wrong?
Thanks
Firstly, select CoreDataCloudKitDemo.xcdatamodeld -> Post -> RelationShips, select attachments relationship, on the Inspect panel, deselect Ordered, then do the same thing on the tags relationship.
Secondly, there will be some errors in the code now, because we unchecked the Ordered option, the property of attachments and tags in the generated NSManagedObject may changed from NSOrderedSet? to NSSet?. So we could change these error lines of code like below:
Origin:
guard let tag = post?.tags?.object(at: indexPath.row) as? Tag else { return cell }
Changed:
guard let tag = post?.tags?.allObjects[indexPath.row] as? Tag else { return cell }
Finally, you can run the code now. ;-)
Further more, on WWDC19 Session 202, the demo shows they set both attachments and tags relationships as Unordered, so I think there's something wrong in the given demo project.
I have an old core data version with Allows external storage in Binary data. And i have created a new one where Allows external storage was unchecked. When i tried to launch my app i got an error:
Unresolved error
Error Domain=NSCocoaErrorDomain Code=134140 "The operation couldn’t be
completed. (Cocoa error 134140.)" UserInfo=0xbd5cd20 {reason=Can't
find or automatically infer mapping model for migration,
destinationModel=...
Then I have created a new file in my project - Model.xcmappingmodel. I have selected source data model and target data model.
After that i see
NSPersistentStoreCoordinator error: NSPersistentStoreCoordinator
_coordinator_you_never_successfully_opened_the_database_schema_mismatch
For future context ... writing to CoreData's external storage is broken as of iOS 12. My solution was based off Drew McCormack's comments on Twitter.
It's worth noting that only writing is broken, reading remains functional.
Create a new property eg «original property name»Internal with the same type but with Allows external storage box unchecked.
You now have two options:
Migrate everything on initial startup of the app - ie fetch all objects with a predicate like this «original property name»Internal == NULL && «original property name» != NULL and move the data across (I did this).
Migrate on the fly ie use the two properties in parallel but only write to «original property name»Internal (while niling «original property name»)
Worth noting one last time that your customer's data is safe until they update it. Tred carefully but you should be fine.
I'm facing an issue when trying to create related entities on the post operation of the create step for a entity.
Here is the description of my problem.
There are 3 entities A, B, C in my system where B & C are the related entities(N:1) of A.
On the Create step, in the Post Operation, for the entity A, trying to create the records for B and C by assigning the A's ID(guid) for the look-up(relation). This throws me the error saying Entity Id must be specified.....
Weird thing is the ``same plugin, registered in the same way works fine in my QA environment.
Following is the error that is produced.
Unhanded Exception:System.ServiceModel.FaultException1[[Microsoft.Xrm.Sdk.OrganizationServiceFault, Microsoft.Xrm.Sdk, Version=5.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35]]:` Entity Id must be specified for Update Detail:
Really need help on this....
Thanks in advance..
Check what values you have by debugging. Now, attaching a debug in a plug-in isn't sweet but it's a lot better than guessing or creating log files. Does the entity have an id right before you update it?
It could help to show some code as an example.
In My Data Sync Group there have 2 tables . Let say A and B . some columns of A reference to B table. B is Master Table.
When sync occur table A is do the processing ahead of Table B. So I got the Foreign Key Reference Error.
IS Azure Data sync processing with alphabetic order ?
Any solution for this ?
Thz in advance.
As #JuneT suggested, you might want to post this question in the "SQL Azure Forum" (http://aka.ms/sqlazureforum). When you do, they have asked specifically that you include the following information when asking Data Sync related questions:
Server id: Your server id
Region: Where your Data Sync Server is located/created
Time / Date: Date and time when you encountered the issue
Tracing Id: The tracing id you see in the message in UI