Status list in custom field not syncing correctly #1295
Comments
megahirt
added
Sync feature
user observed
|
If you need further details, or want me to try a particular sequence of actions, just let me know. |
|
Any progress on this? It remains a problem at our end. Thanks! |
|
Hi J -
There is no update on this unfortunately. I wish I could provide a
timeframe but I cannot at this time. Thank you for letting us know it is
still a problem!
…On Fri, Aug 5, 2022 at 9:53 AM J ***@***.***> wrote:
Any progress on this? It remains a problem at our end. Thanks!
—
Reply to this email directly, view it on GitHub
<#1295 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA2I6KIAADPECDLVY52UVLTVXR64LANCNFSM5NRCH3BA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
hey @viverechristus, i am really sorry it's taken us so long to get to your issue. it may not be much, but this bug is currently waiting on this issue to be tested. and although there's still no timeframe on when your issue will be completed, it is next in line 😃 in starting to wrap our brains around this, it would really be helpful to get a little more information from you. the biggest question i have right now, from your screenshots, is whether this issue pertains specifically to the "ICC" option or not. in other words, are there any options that do work, or any other custom fields referencing lists that do work? and if you sync from Language Forge with the bugged option "***21" selected, does it sync as expected or create another bugged option? thanks again, looking forward to getting to this soon! |
|
Thanks! I want to provide helpful feedback, and perhaps I'll be able to do
that before the end of the week. But it will take a bit of testing on my
end (since I don't know the answers to your questions right off). If you
think you've solved this before Friday, please post another reply so I'll
see!
|
|
We definitely can't fix this that quickly because of the nature of the problem, but it is on our radar, and moving closer. |
alex-larkin
added
the
Alex priority
|
@viverechristus Wrapping up testing on my current issue, I should be able to start this one in the next couple of working days. If you're not able to get any other test steps or information provided, that's okay! I will proceed on and see if I can repro the issue with what I've got 👍 |
|
I just confirmed that this is a general problem, not a problem with just a single list item. If I select any list item in the Spelling Status field while in Language Depot, once it syncs into FLEx, the field isn't selected, but there's a new field that's mostly asterisks and then numerals. It appears that the numerals are unique to particular fields. Let me know if you have other questions. |
|
Sorry comm's have been scarce so far. The changes have been significant and in another repo. Here's where all the fun is |
(issue reported via [email protected])
Our Language Forge project is a FLEx project synced to Language Depot, which we regularly sync back and forth with LF. At the lexical entry level, there’s a custom field called “Spelling Status” that references the “Status” list. We have customized that list. In FLEx, thus:
And on LF, thus:
However, when one of these items is added/selected for an entry in Language Forge (say, ICC), when it syncs back to Language Depot/FLEx, a new list item has been created with asterisks and a number. So:
But then it shows up in FLEx as:
If I unselect “***21” and select “ICC” in FLEx, then delete “***21” from the Status List, then I sync up to Language Depot and sync over to Language Forge, things look fine. But then it all happens over again when I select an item from the Status list in Language Forge and sync back the other way.
The text was updated successfully, but these errors were encountered: