Mail merge is implemented using an implementation of XJob interface [1] (SwXMailMerge). Its "execute" method takes a sequence of NamedValues, which is how you pass parameters there.

Extending SwXMailMerge::execute (and SwXMailMerge::setPropertyValue) in sw/source/uibase/uno/unomailmerge.cxx to accept another name-value pair is required for this request. It should basically do a processing of that new pair alternative to what is currently done for UNO_NAME_DOCUMENT_URL.

[1] https://api.libreoffice.org/docs/idl/ref/interfacecom_1_1sun_1_1star_1_1task_1_1XJob.html

(In reply to Mike Kaganski from comment #1)
> Mail merge is implemented using an implementation of XJob interface [1]
> (SwXMailMerge). Its "execute" method takes a sequence of NamedValues, which
> is how you pass parameters there.
> 
> Extending SwXMailMerge::execute (and SwXMailMerge::setPropertyValue) in
> sw/source/uibase/uno/unomailmerge.cxx to accept another name-value pair is
> required for this request. It should basically do a processing of that new
> pair alternative to what is currently done for UNO_NAME_DOCUMENT_URL.
> 
> [1]
> https://api.libreoffice.org/docs/idl/ref/
> interfacecom_1_1sun_1_1star_1_1task_1_1XJob.html

Hi Mike,
I have changed the definition of SwXMailMerge::execute in unomailmerge.hxx

from :
virtual css::uno::Any SAL_CALL execute( const css::uno::Sequence< css::beans::NamedValue >& Arguments ) override;

to:
virtual css::uno::Any SAL_CALL execute( const css::uno::Sequence< css::beans::NamedValue >& Arguments1, const css::uno::Sequence< css::beans::NamedValue >& Arguments2 ) override;

Now I didn't understand "It should basically do a processing of that new
> pair alternative to what is currently done for UNO_NAME_DOCUMENT_URL"
Do I need to run 1 more loop in unomailmerge.cxx and get UNO_NAME_DOCUMENT_URL of Argument2 as well and how to process them? Can you please guide me a little bit? Thanks!

(In reply to Shubham Jain from comment #2)
> I have changed the definition of SwXMailMerge::execute in unomailmerge.hxx
> 
> from :
> virtual css::uno::Any SAL_CALL execute( const css::uno::Sequence<
> css::beans::NamedValue >& Arguments ) override;
> 
> to:
> virtual css::uno::Any SAL_CALL execute( const css::uno::Sequence<
> css::beans::NamedValue >& Arguments1, const css::uno::Sequence<
> css::beans::NamedValue >& Arguments2 ) override;

Why? That is not needed. In addition to trying to change a virtual method (which is a public API), which is impossible, the main thing is that it is not needed. The old "Arguments" is already itself an arbitrary-length sequence of name-value pairs, so all you need to do is to add one more pair into the sequence when you prepare it for calling SwXMailMerge::execute, and then implement the processing of that pair in the function.

(In reply to Mike Kaganski from comment #3)
 
> ...The old "Arguments" is already itself an arbitrary-length
> sequence of name-value pairs, so all you need to do is to add one more pair
> into the sequence when you prepare it for calling SwXMailMerge::execute, and
> then implement the processing of that pair in the function.

So I need to add the pair in SwXMailMerge::setPropertyValue function before executing it. I think that something needs to be done in the elif block in line #934:

else if (pData == &m_aDocumentURL)
            {
                OUString aText;
                bOK = rValue >>= aText;
                if (!aText.isEmpty()
                    && !LoadFromURL_impl( m_xModel, m_xDocSh, aText, true ))
                    throw RuntimeException("Failed to create document from URL: " + aText, static_cast < cppu::OWeakObject * > ( this ) );
                m_aDocumentURL = aText;
            }
But I can't figure out what to do here. Can you help?

Hi @Mike. Can you please help me with my problem so that I can give a patch on this task. Thanks!

(In reply to Shubham Jain from comment #5)

I'm afraid that your questions are too broad, to the extent that it looks like "please solve my easy hack for me". Easy hacks are intended for you to do your homework yourself; the questions are indeed welcome, but they must be specific enough, to show that you understand what to do, and only have some specific problem that you need help with.

If it happens that some specific task is unclear for you, it is OK: LibreOffice codebase is huge, and it has very different areas, with different paradigms, styles, etc. Giving up on any task is fine, and is not something to be ashamed of; we all stumble on tasks where we finally surrender, and let others handle them.

Dear Shubham Jain,
This bug has been in ASSIGNED status for more than 3 months without any
activity. Resetting it to NEW.
Please assign it back to yourself if you're still working on this.