Here is the use case. On our portal we want have a custom field that will show the products they have purchased and not all of the products we offer. I have figured out how to do the first part. The only issue I am running into is if it is a new customer we want to show all the products. Is their a way to do with AQL.
I was wondering if inbound reference would work?
This was my first attempt of doing that:
objectType = "Products" AND "Company" = ${customfield_10234.label} OR object HAVING inR()
The only issue that query shows all the products.
If I do this query it will show the product or products associated with the customer.
objectType = "Products" AND "Company" = ${customfield_10234.label}
Hi @Tim Hall!
To me it seems like you have to different kinds of situations:
1. Existing customers selecting their purchased products
2. New customers browsing all products
How I would solve it would be to just have two different custom fields, one that filters and the other that doesn't, and then use a dynamic form to have the user check what they want to do (Existing vs New)
Is there a special reason for you to keep it all in the same field? Or would you just prefer it to be as light of a form as possible?
I was thinking what you're recommending was the solution and it was to try to keep the form as possible. Plus I was wondering if you could even do what I am asking with AQL.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.