ContributionsMost RecentMost LikesSolutionsRe: Expressions in Column Filters Sometimes its so simple :) Thank you. I had tried lowercase 'or' but never upper. That appears to be working. -- Scott Pugh Jennason LLC | Principal Minneapolis, MN | (704)763-0703 www.jennason.com Re: Using Shared field in Multi SelectAppreciate the feedback Don and Evan. I guess my focus is more on the use of the 'Shared field' concept and that role-based data rules don't appear to apply to that concept. My assumption is this behavior would be the same if I was using the 'Shared field' concept as part of a multiple choice field... So good feedback on using relationships for the specific scenario- but still have a concern that the 'shared field' concept appears to be a loophole around Role based data visibility rules- such that I need to go back and and review all uses of Shared fields across my apps... Seems like since such effort was put into the data visibility rules it should be the 'end-all-be-all' anytime a user is viewing data ------------------------------ Scott Pugh ------------------------------ Using Shared field in Multi SelectWant to confirm if the behavior I am seeing is repeatable by others and also if others believe this is a bug I have roles set up in app which limit the view and modify access to records in Table A based on a custom rule In Table B I have a multi select field which is set to leverage the key field of Table A. When I view the mulit select field I am able to see ALL records in Table A. My hope was I would only be able to see the key field value for records in Table A which my user's role has access to view. In other words QB seems to be ignoring the role custom rules when a field is used as a shared field in another table. Thanks to anyone who can confirm they are seeing the same behavior and if you also believe its a bug. ------------------------------ Scott Pugh ------------------------------ What role permission drives the ability to click on column headers to sort/groupTrying to figure out what role setting determines if a user in that role can click on table column headings and choose the sort/group options. I have an admin role that I can do it and then a non-admin role that is unable to do it but can't nail down what exactly in the role definition is driving this... is it at the role level? table level? report level? thanks. ------------------------------ Scott Pugh ------------------------------ Re: International Character SupportAn update in case it helps others.... the 'official' response from QB is that natively this isnt supported as only single-byte characters are currently supported BUT that it is something QB is working on to support in the near future. In the meantime I did discover a workaround that seems to work for my needs- although may still be dependent on customer's browser settings. In my external service that is managing these strings and making the QB API calls I did two things: 1. First I HTML encoded the strings 2. Then, I base64 encoded the strings I sent the base64 encoded string through as part of the XML payload of the addrecord API call. On the QB side I created a formula- rich text field which decodes the base64 string... the result is an HTML encoded string that displays correctly in the rich text field ------------------------------ Scott Pugh ------------------------------ International Character SupportHaving some trouble getting a text string into QB that includes international characters. Here is the original string:LÉČIVA 5 UI/ml soluţie injectabilă I have confirmed that if I copy/paste this into a Rich Text field I can store and view it within QB with no issues (interestingly a regular text field does NOT work) My challenge now is I am sending these strings into QB via the addrecord API... The XML used in the body of the API call to add this field is below. I've confirmed it is the correct UTF-8 encoded string: <field fid="xx">L\xc3\x89\xc4\x8cIVA 5 UI/ml solu\xc5\xa3ie injectabil\xc4\x83</field></qdbapi> However when sending in via API the resulting text in QB appears as: LÉCIVA 5 UI/ml solutie injectabila Just trying to figure out if this is something I"m doing wrong in the API call...or if this is the expected behavior of QB. ------------------------------ Scott Pugh ------------------------------ Re: Unable to copy file upload field value to another table in Automation editor I think you're on the right track.... i thinkyou just have to add a ? before the &usertoken... good early results...will keep you updated -- Scott Pugh Jennason LLC | Principal Minneapolis, MN | (704)763-0703 www.jennason.com ------Original Message------ jennason.quickbase.com/up/ bp5gujqc5/a/r3672/e522/v0&usertoken=xxxxxxxxxxxxx try the above ------------------------------ Mark Shnier (YQC) Quick Base Solution Provider Your Quick Base Coach http://QuickBaseCoach.com mark.shnier@gmail.com ------------------------------ Re: Unable to copy file upload field value to another table in Automation editor Admittedly I'm making an assumption as I havent yet tried this... But if I put the URL (replacing the xxx's) https://xxxxxx.quickbase.com/up/xxxxxxx/a/rxxxx/exx/v0 into a webpage it (understandably) forces me to login first before it downloads a file I will be calling that URL from a web service to stream the file contents to the service, which then does some other things with that file.... my assumption (this is what I havent tried) is that it will error out because I"m not providing any authentication.... Or maybe a better way of saying is I actually hope it will error out because I havent provided any authentication normally in my QB API calls made from external services I'll include the user and apptoken.....but how/where do I include the user and apptoken in this URL? https://jennason.quickbase.com/up/xxxxxx/a/rxxx/exxx/v0 -- Scott Pugh Jennason LLC | Principal Minneapolis, MN | (704)763-0703 www.jennason.com ------Original Message------ Sorry, but if there is an API call that you can use, why are you saying that you cannot supply a usertoken to deal with permissions? ------------------------------ Mark Shnier (YQC) Quick Base Solution Provider Your Quick Base Coach http://QuickBaseCoach.com mark.shnier@gmail.com ------------------------------Re: Unable to copy file upload field value to another table in Automation editorMark- This does answer my question up to the point of permissions... really what I'm trying to do here is download a file attachment from QB (which then is sent off to an email program as an attachment). So all of my work is happening via an external service that is calling QB APIs....so using your post I now understand how I can build the URL to download the file attachment- but normally I would be including a user and apptoken in my API calls.... doesnt seem like I can do that in this case? So not sure how to proceed- and don't love the idea of making the file attachments EOTI ------------------------------ Scott Pugh ------------------------------ Re: File attachment from request form/table to elsewhere in the app via automation/JSApologies if the answer is right under my nose....but if I want to take your suggested approach of just populating the file attachment URL in a text field- what's the easiest way to do that if I don't want to have a button or anything clicked?.... I just want to populate the URL of a file attachment field (latest version always) automatically and assuming there is a file in the file attachment field.... once I do that I would then share that field down to my child table and then I'd be good to go (for what I need to do) Thanks for the help ------------------------------ Scott Pugh ------------------------------