We use an external setup that sends information on our orders into Podio and from there we manage them. We have had an issue with our Email field and it's lead to the External ID 'email' being lost (we are up to email-6' now before realising the issue). Is it possible to reset/restore the External ID to be 'Email' instead of 'Email-6' and if so could you please point to how we can do it. The developers we use don't work with us anymore so it's a bit of a nightmare to sort out. We are reasonably tech savvy but not wiz kids by any stretch of the imagination. I've copied below what our old developers said:
"What I'm pretty sure is your case, is that you have deleted the original Email field from the template, and now you are trying to put it back. The problem is that, only by appearance, you have a single Email field in your template, but when Fabnami is sending the data, the collected customer email is attached to the field with external ID "email", not the one you have only labeled as Email. The result is that podio will exhume the deleted field and will display it using the last labels it has. In your case there will be the original field with label "Email" and ExternalID "email" plus a second empty field with label "Email" but different External ID."
I hope you can help :)
Each time, when the field get created, external_id get created in parallel(1 to 1 mapping). If you delete the field the external id get deleted along with that. You can't reset the external id "email" to "email-6".
There is a option to recover the first deleted field "Email" -> external is id "email", but with the recovery payment.
Each time, when the field get created, external_id get created in parallel. If you delete the field the external id get deleted along with that. You can't reset the external id "email" to "email-6".
There is a option to recover the first deleted field "Email" -> external is id "email", but with the recovery payment.
Related
We have a table that contains a user's email address, their first name and last name and some date columns. The standard search works great for those.
I would like to provide a way of the user being searchable by their user id which is a GUID. The user id is not a visible piece of data. This search would really only be used by admins
I know I could use the data-search attribute on the user name column e.g.
data-search="43b30438-e3c8-4e27-8b31-5fcc52e53a3b me#test.com"
However that makes that row and any other row findable with just the number "43" as that GUID starts with 43 or "52" because it has a 5 followed by an 2. That is clearly not what I want. How do I make the users searchable by their GUID as well as their username but in the case of the GUID only when it is the whole GUID being searched for?
Thanks
I have a cabinet say "tcabinet" in a repository "trepository".
In this repository there are multiple users however their access is restricted by adding the cabinet IDs to the restricted_folder_ids column in dm_user object.
The user has access to the ACL. But still they can not see tcabinet as their access is restricted. There are thousands of such users.
For these users to see the tcabinet. I'll have to add the object id of tcabinet to restricted_folder_ids column of each user which would definitely be a large task.
Is there any way to make them able to see the cabinet without adding the cabinet id to each user?
As confirmed by OpenText also, there is no other way to achive this. However we can add the cabinet to everyone's 'restricted_folder_id' attribute in dm_user table.
UPDATE dm_user object
APPEND restricted_folder_ids=’<Object ID of the Cabinet>’
WHERE user_name='<user_name>'
NOTE: If you are using this method, make sure to filter out the users which does not have any existing 'restricted_folder_id' in dm_user table, else this method will restrict the access of these users to a single folder which might not be the intention.
I have this table used when a user writes a note.
When writing a note, the user specifies if a sell-department and/or a buy-department should receive the note.
Each user can create a Case (lets say its just a table with case_id and case_text). And the notes the users write are related to a case.
So the table NOTES is (postgres database) something like this:
ID
TEXT (the message itself)
USER_ID (the user that writes the note)
CASE_ID (the case_id for which the note is been written)
Short word about users:
There are "ordinary" users and those working on a department. This should not make big difference for the description here.
When an ordinary user writes a note, let's say he want both buy-department and sell-department to be included (being informed about the note/see the note).
What happens now is that there is another table called UserNotes. It looks like this:
ID
IS_READ
NOTE_ID
USER_ID
DEPARTMENT_ID
READ_AT_DATE
So ordinary user with id = 1 writes this note and in the code (as he tells sell and buy-departments have to be included) I search for all the users working at that specific sell-department and all those working at that specific buy-department. I then put all these users in the table UserNotes. With IS_READ false by default.
When a user in the specific sell-department reads the note, I will then change IS_READ for this user's entry in UserNotes.
This is how it works today. I don't think this is scalable. I'm already getting performance issues. I don't think it is important to know when a note has been read. So because of this I was thinking that maybe the following solution could work. Please have a look and tell me if it could be better and the current one or if you have some other suggestion please let me know:
I drop UserNotes table. I add a new filed in table Notes: READ_BY. Here I will update the field each time a user reads the note.
I don't know if I could use some postgres-specific thing, maybe making this field a json-string and searchable.
i have a User model and some common columns, such as name, email, password, etc.
and here is the thing:
i donot want a user changing his email address after signed up, what should i do?
just don't include the email field in the update form?
and i think the attr_accessible is not for this use either.
what do you suggest? thanks a lot.
What you need is
attr_readonly
The documentation says the following
Attributes listed as readonly will be used to create a new record but update operations will ignore these fields.
So, a new record can be created with an email but you can never change it (without a hack) after the record has been created.
I run a forum which I built myself. Ok so all users have the opportunity to delete themselves.
But all their threads and posts will remain. But right now where it should say their username it's just blank.
How should I handle this?
Should I make a new user and call it e.g. "deleted user" and assign all threads/posts to that ID when they delete themselves?
Or should I just check if the user ID exist if not print e.g. "deleted user" as username?
What's the smartest way? Any other ways tell me.
Thanks!
p.s (i'm not a native english speaker, looked up some fancy words on a online dictionary)
I would suggest not actually deleting the user. You could simply add a column to the users table such as:
ALTER TABLE users ADD COLUMN (is_active TINYINT(1) NOT NULL DEFAULT 1);
Then when you "delete" a user, simply mark them as inactive:
UPDATE users SET is_active = 0 WHERE users.id = 7;
For user listings, and account access you would check the is_active status. For displaying of data such as posts and what not, you'd not care about their active status, youd just grab the name from the table.