Hello everyone!
Sometimes when we import elements, usually coming from another Revit model, the connector asks to map the new types. Would be awesome to have the option to create the new type if the family is loaded into the project, duplicating an existing one and changing the name.
I’m not asking to set the parameters into the type because sometimes they are not created within the projects (project parameters and shared parameters).
Ok, let me know what do you think! 
We are collating suggestions for the next phase of the Mapper initiative so this is a good one to add to the list - I don’t have a timeline for you as there are a tonne of other connectors goodies coming down the pipe rn but @gokermu will be certainly interested 
Hey @efdiloreto ,
Just to clarify, if the project includes family but not the type, do you want Mapper to create those types for you by duplicating an existing type and updating it’s parameters? Do you think this would be limited to System families (e.g. Walls, Floors, Ceilings etc.) or for Component Families too?
Hi @gokermu!
I think it’s easier for system families because they exist in all models. Component families need to be loaded into the document and have the correct category.
Regarding the parameters, it would be awesome to update them, but in some cases, they might not exist in the project (Project parameters and Shared parameters).
I have another idea @gokermu . Just let me know if it’s possible to implement.
What about receiving types from Project Information?
@efdiloreto, a lot is possible, but we should approach it with specific use cases in mind. What use case can Speckle fulfill that other methods are not already fulfilling?
Usually we have really big projects when we need to split a model in several models. Since they are parto of the same asset need to “share” a lot of common information between them.
But I think this feature might be very specific. Not sure if anyone is having the same problem.
talking about replacement of families and types I think Speckle could go ahead and use a extended Library ( either a sharepoint or local) connected to the Specke-Manager. every time loading a project where families or types are missing in it. the first request should go to check if this family might exist in that library.
next step could be a good UI to see the different families and types. by Highligthing missing types we could decide should that missing type be replaced by another while keep the name. or creating something different( would like to avoid those -because families are parametric and complex - Imports are just 3D-Meshs)
after importing, we could get a list of replaced items with type and family names and the used Paramters.
Parameters are for sure challanging. In Revit there is a strikt way to create a shared parameter and when done wrong, this can not be replaced. first thing could be to get the shared parameter from the uploaded model and store it inside the Project. that could be the ressource for creating new paramter in the new project. but there are a lot of issues can happen in that process.
but a very importend topic to discuss further
Great insights @HeinrichBoldtGetinge . I agree with your point on shared parameters being challenging. So for now, we are not creating them at all 
. With the next-gen Revit connector, we are rethinking the workflows we support. So I’d appreciate your feedback on how we are publishing data from Revit and how it’s structured.
Download Next-Gen Revit connector