12th Feb AMA: I'm Courtney Youngblutt, Xplan Design Consultant & efficiency expert, Ask Me Anything!
Hi Courtney,
Can you please assist in setting up templates for OFA's? We have the Fee Consent Section pre-filled for our client base. If there is coding somewhere I have not been able to find it.
It appears that the data is captured across two screens. i.e. amounts, dates etc.
We also want to know how we can code this out into an agreement (Merge doc output) for the Services entitled, where is the best place to save this as not all of our clients are on Platform consent, some will be on Direct Debit. Can this possibly be saved as a benchmark text and dropped into this section?
Are you able to provide the coding for these fields?
Thanks
I tried the code from John Roughton's post and it is only populating ID's and nothing else from the full list of coding. as below
<:let account = $client.fee_consent_account:> Fee consent id: <:=account[‘fee_consent_id’]:> Account id: <:=account[‘account_id’]:> Required: <:=account[‘required’]:> Created by: <:=account[‘created_by’]:> Doc id: <:=account[‘doc_id’]:> Status: <:=account[‘status’]:> Consent next date: <:=account[‘consent_next_date’]:> Consent sent date: <:=account[‘consent_sent_date’]:> Fee start date: <:=account[‘fee_start_date’]:> Fee end date: <:=account[‘fee_end_date’]:> Consent signed date: <:=account[‘consent_signed_date’]:> Advice fee: <:=account[‘advice_fee’]:> Amount: <:=account[‘amount’]:> Amount Percentage: <:=account[‘amount_perc’]:> Advice fee frequency: <:=account[‘advice_fee_frequency’]:> Is fee estimated: <:=account[‘is_fee_estimated’]:> Estimate description: <:=account[‘estimate_description’]:> Services entitled: <:=account[‘services_entitled’]:> Provider status: <:=account[‘provider_status’]:> Sent to provider date: <:=account[‘sent_to_provider_date’]:> Processed date: <:=account[‘processed_date’]:> Processed date: <:=account[‘processed_date’]:>
- courtney.youngblutt3 months ago
Iress Contributor
For the xmerge syntax, the code in John Roughton’s article should work. Note though that there are 2 different sets of code, depending on whether you are merging the template from the Fee Consent area (if you are, you need to link the template to the Fee consent template section in the area shown in the above screenshot) or you are merging it as a normal xmerge template from the merge reports area of a client record.
<:let account = $client.fee_consent_account:> will only work if the document is saved as an Xmerge template and linked to the Fee Consent area.
<:for account in $client.fee_consent_accounts:> should be used if wanting to merge the template from the merge templates area
If you are still struggling with the code you can raise an Xmerge Connect request through Iress Connect and the team can help you out.
(If the above does not make sense, please let me know!! And I can try to explain it again. 😁 )
- courtney.youngblutt3 months ago
Iress Contributor
sally.warncken - xmerge code for the fee consent area. 😊
- sarah.burke383 months agoVisiting Enthusiast
Thank you Courtney, yes I've tried everything i can to get the code to work. I need help looks like I will need go through Iress connect as I thought I had chosen the Fee Consent area coding. would be good if the code and instructions could be included in the coding library.
- courtney.youngblutt3 months ago
Iress Contributor
Thanks Sarah -send it through and I'll give the Technical Services team a heads-up that it is coming. The team are in the middle of updating the coding library at the moment so your feedback is very timely! I'll pass it on and get the details added so it is easier to find. Thank you!!
- courtney.youngblutt3 months ago
Iress Contributor
felicity.eardley - see above for details on the xmerge code for the OFA & Fee Consent area.
Welcome to this AMA thread!
Here's how to get involved:
- Submit your questions: Just type them out and post now ahead of the AMA! This is a text-based event, so no audio or video is needed. The expert will be online to answer whatever questions you have during the scheduled time.
- Be respectful: Keep it friendly and professional. Respectful dialogue makes the AMA enjoyable and informative for everyone.
- Stay engaged: Feel free to follow up or ask about different topics as the thread goes on. The more you interact, the richer the conversation.
- Enjoy the experience: Use this opportunity to gain insights and connect with peers and experts. Let’s make this AMA one to remember!
Looking forward to all your amazing questions and let the asking begin!
Recent Discussions
9th Apr AMA: I'm Sarah Jacobs, Xplan optimisation expert and product manager, Ask Me Anything!
With the government proposing to replace SOAs with Client Advice Records (CARs), are your advice document processes in Xplan as efficient as they could be? For example, curious about how to optimis...sarah.jacobs21 days agoIress Contributor709Views4likes18Comments27th March AMA: I'm Lana Graham, Xtools+ expert and product manager. Ask Me Anything!
Xtools+ has helped countless advice practices work out solutions to their clients' financial problems – even for the most complex scenarios. Why not fully harness its potential and have a say in what...lana.graham24 days agoIress Contributor870Views3likes43CommentsAMA: I'm Jess Lamb, Xplan expert and Director at Practice Dynamix, Ask Me Anything!
Advisers and paraplanners, are you providing the best possible experience during the client review? And how could you be using Xplan to be making the process even more efficiency? Join me here on T...jessica.lamb28 days agoAdvisely Partner624Views5likes22Comments13th March AMA: I'm Jason Zhang, Xplan Portfolio expert and product manager, Ask Me Anything!
Managing client portfolios effectively is essential for a well-run advice practice – but are you using all the features available to you in Xplan? Make 2025 the year you fully harness Portfolio's pot...jason.zhang2 months agoIress Contributor499Views6likes17Comments