I was still having issues and have opened a case with support. I’ll add what I learn here when we figure this out. But I’ve marked your reply as best answer @jhouser. I didn’t have issues creating customer groups for a client recently and thought it was fairly straight forward using A type restrictions. It seems like it should be very similar for this exercise. I’m not sure if there’s a build specific problem, or if it has something to do with the nature of system processing records (AR flows through that default subaccount). Any group, even just one, seems to restrict that subaccount or trigger errors, even if I make the group to specifically allow AR access to the subaccount. The only time I don’t have problems is if I turn off all GL groups (all my attempts). Then everything behaves the same as it does without ever trying to enable the groups.
@jhouser thank you! I will try this and advise back.
I took another approach with requests for multiple report versions. You could also create a customization with an action for each report version, combined with a condition field that looks at the branch for the document. If its not the appropriate branch you can set that action to be hidden, and the action is tied to the specific report for that branch.
I had a similar error when attempting to save a new snapshot on top of a U100 dataset. Support advised me to remove the path and storage provider information from the Update Preferences screen.If you are able to remove the provider and folder path and turn off the use update server, I believe you’ll be able to save the snapshot.
I’ll reach out to the client and bank contact to confirm. Thanks @bryanb39
@bryanb39 actually I tried setting that feature on the data provider to True. Not only does it put a set of quotes on every field, even the column headers (if left enabled) comes out with quotes on them.If I have it set to False, no quotes are added to headers or data. The Concat command appears to show the single quotes I’m looking for. Upon running the export and retrieving the file however, the payee field is coming up like this:"""ABC Solutions"""Something in the translation is causing additional quotation mark sets to be tacked onto that field.=Concat('"',[Results.APContact_fullName],'"') is the formula I have set in the export scenario, coming from a GI. I have also tried putting that logic into the GI first but end up with the same result.
@msw21 Thanks for that suggestion. I’ve not spent a lot of time with ARM reports but I can reach out to colleagues to review.
@iqraharrison48 I’ll give that a try as well (reset the cache) and also my browser. It is odd, and I’m still searching to see if I can find an explanation for the differences. Thanks again.
@Debbie Baldwin and @iqraharrison48 I explored two different sites running 22.205.0026, and found one the hyperlink works and the other it does not. I’ve also checked newer versions than this build and so far they are working. I could consider putting in a release upgrade for them but was curious to see if anyone else had experienced the problem before. I’ve got 22.208.0012 on a dev site that the hyperlink works, for instance.
@Robert Sternberg thank you Robert, that’s actually what I was attempting to do. I’ll see if I can get this moved there or post it again!
Thank you both for confirming this for me. I will put the idea in for future consideration!
Already have an account? Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.