No. I was on b23. b24 works fine. Thanks
Downloaded the bug fix and all is well. THANK YOU for the quick turn-around on this! It is much appreciated.
I have two addition errors that are major issues for me.
- When I’m removing items from my database, I search using NEW SELECTION pulldown (upper left) then fill in the search box. If I have not set the first search criteria correctly, it used to be that after filling in the data box, I could use the pulldown to find the right criteria (column) to search. Trying that now I get an error message: Internal error in dialog logic. Field or Variable (dlgTrigger) does not exist.
This can be fixed by making sure I have the criteria properly selected before entering the data in the search box, but that hampers the program. Does work though.
- More important issue is that I used to create a list of items to remove from the database. Now I can only enter one item at a time, using the instructions above.
Assuming I’ve got my first item identified to remove from the database, I used to be able to change “New Selection” in upper left to “Superset Of Current Selection” and then enter the data for my 2nd search, hit enter and it would add it, so I now have 2 items in my list of items to delete. I often have 20-30 items to delete and this is the easiest method I’ve found, then I would use the “delete” X to remove each one by one.
Now when I try to add a 2nd item I get an error message, even though when searching with “Superset of Current Selection” selected, the note in upper right corner says “2 matches from 53,834 records” and it shows both of the items I want in my list. But entering “select” I get that same error code again (Internal error in dialog logic. Field or Variable (dlgTrigger) does not exist) and no apparent work around. Which means I have delete one item at a time which is not going to work given my use of the database.
Help!
Have you upgraded to the b24 release that was uploaded last night?
Sounds like Jim’s latest fix (v. 24) will fix this. But if I understand what you’re trying to do, you might review select reverse and remove unselected.
Yes, did that this morning before attempting my database updates.
No, the latest update didn’t fix this. And not sure what you’re suggesting, sounds like you’re suggesting somehow select everything (53k lines) that are NOT the ones I want to remove? Seems like an odd way to remove specific items. Would prefer that the select items function work properly.
I reinstalled b23 on my computer and was able to duplicate the problems you are describing. But when running b24, everything works fine. I think somehow you are actually running b23, not b24. Maybe you somehow have more than one copy of PanoramaX.app on your computer? Please make sure that you have only one copy of PanoramaX.app on your computer, and that it is the b24 release.
MY APOLOGIES! Although I downloaded and updated, for some reason the update didn’t “take”. When I just reopened my file it gave me the update message again and asked if I wanted to install (since I’d already downloaded it) and restart. Did, and all is bliss in my Panorama world again. Thanks!
While I’ve got your ear, did the issue ever get fixed where setting a field to “no duplicates” doesn’t seem to have any effect? No “ding”, no nothing. That was my biggest complaint and still is, but perhaps there’s a fix or workaround now?
From the Panorama X 10.2 public beta FAQ page – Panorama X 10.2 Public Beta Frequently Asked Questions
To learn more about this see the help page.
Panorama X 10.2 is a huge upgrade, it is well worth taking some time to study the release notes.
Not fixed. That feature (enabling “no duplicates” in a field) is there, but it’s not been implemented. Still. Unless I’m missing a trick, enabling No Duplicates still does nothing, there is no warning given (the FAQ says it’s “supposed” to provide a warning). It still does not.
Going to the discussion forums there’s a thread about this that says as of 2020 it still has not been implemented (lots of us needing it) but that was the last post, no update since then.
If I set a field to No Duplicates, and then try to enter a duplicate, I get this.
This feature applies to manual entries that you type or paste in. It does not apply to imports or procedures assigning a value to the field.
I think I know the thread you are referring to, since you participated in it, and that’s not what I am seeing.
Panorama 10.2 is the “next version” that is being referred to.
I had my own screen shot ready to paste in, but Dave beat me to it 
This feature is definitely implemented in Panorama X 10.2.
Here’s a screen shot showing my database. Why is it allowing duplicates?
Here’s the forum thread in the “help” menu that I’m referring to where it says still not resolved.
I’m not sure why you’re getting different results in the database, and in the forum thread. Help!
Is there a “notifications” checkbox I have to set somewhere in order to have the notifications box appear? Why would yours bring it up, but mine does not? I am ONLY using the final field (Item Number) with the No Duplicates feature as all other fields can/should allow duplicates.
Why would you assume that an old forum thread that hasn’t been updated in over a year would contain valid information about a new release that has only been out for 10 days? We don’t go around updating old forum posts to reflect every change made to Panorama. However, if you did follow the link in that thread to our issue tracker, you would see that the issue tracker was updated to show that this was resolved.
And in fact, the old forum thread does mention that this issue has been resolved, but the fix hadn’t been released yet. With the release of the 10.2 public beta, this fix is now available to all Panorama X users.
Is there a “notifications” checkbox I have to set somewhere in order to have the notifications box appear?
No, there isn’t. It always shows up.
Why would yours bring it up, but mine does not?
I notice that the three records at the bottom of your example are EXACTLY identical across all fields. I’m guessing that you didn’t type this information in three times, but used copy/paste record, or duplicate record. The no duplicates feature only works for data that is typed into the field. It does not work for importing data, copy/pasting entire records, data that is put into a field via programming code or anything else except data entry into the field. This is the same as earlier versions of Panorama have always worked.
Thank you, yes. I appreciate your attempts to help! The old forum thread said it’s going to be fixed with the new release, I did see that as I’ve read it top to bottom. And I’m asking for help because my version of the new release isn’t working correctly.
The 3 duplicates I entered were all typed in by hand, nothing has been cut/copy/pasted, imported, or anything else. The only reason I populated the other fields with identical info was just in case there was a question about how those fields operated. Here’s a new screenshot. I’ve just added 5 items to the Item Number field. All identical, entered now by hand. No notification. I must be missing something simple and silly for it not to work, but I cannot for the life of me figure out what it might be!
Is there a setting in that field that you can see that I need to change? Also, this probably needs not be said, but I’m running on a Mac with OS Big Sur 11.6
The problem is that you have set the data type to Choices. If you change the data type to Text it will work. Looks like this is a bug, but in your case the Choices type doesn’t make any sense anyway, so you should just set the data type to Text. In fact certainly it would never makes sense to use Choices and No Duplicates on the same field. It might make sense to use Choices with No Unique, however, and that does not work either.
I have created a new bug report for this.
PERFECT! TBH I didn’t think about the difference as I didn’t really know what “choices” meant and the database worked fine (other than the duplicates issue!). I’ve fixed it.
Thank you very very much!
For future reference.