nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Need to have blank default value for data source value when we define data source in modular

gauravTsDev

Hi ,

I have customised my own data source but when I add it in modular then all drop down values get reflected in default value field but if you use teamsite provided data source default value field is blank.So is there a way we can have default field completely blank in case custom datasource and drop down value only visible at instantiation screen.Pls see screen shot

Thanks

Find more posts tagged with

Comments

Adam Stoller

Perhaps if you posted the code (as an attachment) someone here might be able to figure out what you're doing [wrong] and how to fix it.

gauravTsDev

Hi ,

Pls my code below :

I am just adding value in map and returning.

.........................................java code........................................

import com.interwoven.datasource.ArrayDataSource;
import com.interwoven.datasource.MapDataSource;
import com.interwoven.datasource.core.DataSourceContext;
import com.interwoven.cssdk.common.CSClient;
import com.interwoven.cssdk.common.CSRemoteException;
import com.interwoven.cssdk.common.CSException;
import com.interwoven.cssdk.common.CSIterator;
import com.interwoven.cssdk.access.*;
import
com.interwoven.cssdk.factory.CSFactoryInitializationException;
import com.interwoven.cssdk.filesys.CSVPath;
import com.interwoven.cssdk.filesys.CSBranch;

import java.io.FileWriter;
import java.io.IOException;
import java.util.*;

public class sampleDataSource implements MapDataSource

{

   @Override
   public Map<String, String> execute(DataSourceContext context)
   {
       String sessionId = context.getSessionId();
       String vpath = context.getServerContext();
       Map<String,String> params = context.getAllParameters();

       Map test = new HashMap();
       test.put("usr1","rahul");
       test.put("usr2","sudhir");
       test.put("usr3","mahesh");

       FileWriter out = null;
       try
       {
           out = new FileWriter("/opt/Interwoven/TeamSite/tmp/demo.log");
           out.write("dsn execution start");

           for (Map.Entry<String, String> entry : params.entrySet())
           {
               out.write(entry.getKey() + "/" + entry.getValue());
           }

       } catch (IOException e) {
           // TODO Auto-generated catch block
           e.printStackTrace();
       }

       // TODO Auto-generated method stub
       return test;
   }

}

Adam Stoller

gauravTsDev wrote:
I am just adding value in map and returning.
.........................................java code........................................
[...]
public class sampleDataSource implements MapDataSource
{
   @Override
   public Map<String, String> execute(DataSourceContext context)
   {
[...]
       Map test = new HashMap();
       test.put("usr1","rahul");
       test.put("usr2","sudhir");
       test.put("usr3","mahesh");
[...]
}
}

Since you're explicitly making your own hashMap for the menu items - why not just add a blank one?

    public Map<String, String> execute(DataSourceContext context)
    {
        [...]        
        Map test = new HashMap();
test.put("", "");
        test.put("usr1","rahul");
        test.put("usr2","sudhir");
        test.put("usr3","mahesh");
        [...]
    }

gauravTsDev

Thanks, It didnt worked as expected ,pls see the screen shot .

Adam Stoller

Clearly something is manipulating the contents of the HashMap you're returning from your code to inject the information that appears to be showing there.

You could try using a TreeMap for the object to be returned (I'm looking at an example of some code I used on a project and that's what I used there):

    public Map<String, String> execute(DataSourceContext context) {
        Map<String, String> result = new TreeMap<String, String>();
        result.put("", "");
        result.put("usr1","rahul");
        result.put("usr2","sudhir");
        result.put("usr3","mahesh");
        return result;
    }

In the actual code (once you're done testing things) there's obviously a lot more to do, including adding diagnostic logging, but for now - see if the above works.

Rick Poulin

Doesn't matter what you pick in the modeler dropdown if you have a custom_instantiation.cfg that controls the instantiation form the way you want it...

mgammon

I just went through a similar issue where I wanted a datasource entry to display with label of " ---------------" and value of "" (empty string). This entry kept getting stripped from the select list because the DCT JS code that processes the result of the datasource call (dcapi_datasource.js) skips any entry that has a null or empty value due to the way it splits "=_iw_=".

To get around this issue we put in a single hyphen for the value (i.e. "-") and just substituted it in our datasource callback function. You might be able to do similar.

Example:

function setDatasourceValueCallback(resultObj, returnParams) {
	// MANIPULATE resultObj here...
	resultObj = updateKeyValues(resultObj);

	...
	// continue processing
}

function updateKeyValues(resultObj) {
	// manipulate and return IWMap resultObj
}

gauravTsDev

Hi,

Actually I am not using dynamic call back .Here its static inline call.Problem is that when we define datasource variable in modular then the default value field pre -populates the drop down with separated by iw but when u use teamsite provided data source then default value field completely blank.Also on instantiation screen this iw separated value appears as we are bound to select any default field value while defining dsn in modular so ideally it should be blank.

mgammon

Regardless of whether you are using a dynamic callback, if the datasource still processes through the parseComponentValuesToObject() function in dcapi_datasource.js then any member in your HashMap with an empty string for "value" will get discarded. You can test to see if this is what's happening to you.

The culprit function is below which is in dcapi_datasource.js. Use IE debugger and put a breakpoint at beginning of function and observe value of "componentValues" as it enters function. If the member from your HashMap is present there but fails to get populated into the "resultObj" object then what I described above is what's happening to you. For us we used a callback as a workaround. You may choose different method to work around it but here will be your root cause.

[edit] I've bolded the lines where the value/label pair is split apart and evaluated. If your datasource is routing through this function then this is where an empty "key" in the HashMap would be discarded.

function parseComponentValuesToObject(componentValues)
{
    var resultItemArray = componentValues.split(";");
    var arrayLength = 0;
    if(resultItemArray.length == 1)
    {
        arrayLength = resultItemArray.length;
    }
    else
    {   //Last item is null so ignore it
        arrayLength = resultItemArray.length - 1;
    }
    var resultObj;
    for(j=0;j<arrayLength;j++)
    {
        if((resultItemArray[j] != null) && (resultItemArray[j] != undefined))
        {
var resultItemValue = resultItemArray[j].split("=_iw_=");
            if(resultItemValue.length == 2)            {
if((resultItemValue[0] != null) && (resultItemValue[0] != undefined) && (Trim(resultItemValue[0]).length > 0))
                {
                    if(IWMap.prototype.isPrototypeOf(resultObj))
                    {
                        resultObj.put(resultItemValue[0],resultItemValue[1]);
                    }
                    else
                    {
                        resultObj = new IWMap();
                        resultObj.put(resultItemValue[0],resultItemValue[1]);
                    }
                }
            }
            else
            {
                if((resultItemValue[0] != null) && (resultItemValue[0] != undefined) && (Trim(resultItemValue[0]).length > 0))
                {
                    if(Array.prototype.isPrototypeOf(resultObj))
                    {
                        resultObj[resultObj.length] = resultItemValue[0];
                    }
                    else
                    {
                        resultObj = new Array();
                        resultObj[resultObj.length] = resultItemValue[0];
                    }
                }
            }
        }
    }
    return resultObj;
}

gauravTsDev

Thanks for suggestion the js that you have provided must have been helpful to handle drop down values on instantion screen .But I wonder if there is any work around in java class so that we can forbid dropdown value population in default field in modular where we configure datasoure because as soon as you select your custom dsn these values pops up and your bound to select any one value.